| commit | 40208351e0617a978f8bd16bdca7753714a2fcc8 | |
| 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, 17 Dec 2010 11:29:44 +0000 (17 11:29 +0000) | ||
| tree | 7ecc41f8814027b22ed071058820e56889046672 | treesnapshot (tar.gz zip) |
| parent | d677f8a948d0aac135854e136ddbb1eebbad3632 | 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 |