diff options
| author | Anthony Liguori | 2011-08-22 15:24:58 +0200 |
|---|---|---|
| committer | Anthony Liguori | 2011-09-02 17:34:55 +0200 |
| commit | 12d4536f7d911b6d87a766ad7300482ea663cea2 (patch) | |
| tree | 848fe9cb11b82145fae05ee05aace4f90a3564af /linux-user | |
| parent | trace: fix out-of-tree builds (diff) | |
| download | qemu-12d4536f7d911b6d87a766ad7300482ea663cea2.tar.gz qemu-12d4536f7d911b6d87a766ad7300482ea663cea2.tar.xz qemu-12d4536f7d911b6d87a766ad7300482ea663cea2.zip | |
main: force enabling of I/O thread
Enabling the I/O thread by default seems like an important part of declaring
1.0. Besides allowing true SMP support with KVM, the I/O thread means that the
TCG VCPU doesn't have to multiplex itself with the I/O dispatch routines which
currently requires a (racey) signal based alarm system.
I know there have been concerns about performance. I think so far the ones that
have come up (virtio-net) are most likely due to secondary reasons like
decreased batching.
I think we ought to force enabling I/O thread early in 1.0 development and
commit to resolving any lingering issues.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'linux-user')
0 files changed, 0 insertions, 0 deletions