| commit | cbbb9ded64be70444109db7f311027eb8ee0d0f7 | |
| author | Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> | |
| Thu, 11 Nov 2010 13:21:05 +0000 (11 13:21 +0000) | ||
| committer | Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> | |
| Fri, 12 Nov 2010 12:24:14 +0000 (12 12:24 +0000) | ||
| tree | e798ebbfaa743bec4d445a03281abf9fc70cfc0b | treesnapshot (tar.gz zip) |
| parent | ac19eca51bc70ba5534326cc1db21c350ce32097 | commitdiff |
virtio-pci: Don't use ioeventfd on old kernels
There used to be a limit of 6 KVM io bus devices inside the kernel. On
such a kernel, don't use ioeventfd for virtqueue host notification since
the limit is reached too easily. This ensures that existing vhost-net
setups (which always use ioeventfd) have ioeventfds available so they
can continue to work.
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
There used to be a limit of 6 KVM io bus devices inside the kernel. On
such a kernel, don't use ioeventfd for virtqueue host notification since
the limit is reached too easily. This ensures that existing vhost-net
setups (which always use ioeventfd) have ioeventfds available so they
can continue to work.
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
| hw/virtio-pci.c | diffblobblamehistory | |
| kvm-all.c | diffblobblamehistory | |
| kvm-stub.c | diffblobblamehistory | |
| kvm.h | diffblobblamehistory |