| commit | 1e7398a140f7a6bd9f5a438e7ad0f1ef50990e25 | |
| author | Pankaj Gupta <pagupta@redhat.com> | |
| Tue, 16 Jun 2015 08:18:59 +0000 (16 13:48 +0530) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Fri, 19 Jun 2015 10:17:49 +0000 (19 12:17 +0200) | ||
| tree | a321d5ab687fbe83abba5c2dfd83d97051abfff0 | treesnapshot (tar.gz zip) |
| parent | 74de5504fd063019433ec0746105da774ede790d | commitdiff |
vhost: enable vhost without without MSI-X
We use vhostforce to enable vhost even if Guests don't have MSI-X
support and we fall back to QEMU virtio-net.
This gives a very small performance gain, but the disadvantage
is that guest now controls which virtio code is running
(qemu or vhost) so our attack surface is doubled.
This patch will enable vhost unconditionally whenever it's requested.
For compatibility, enable vhost when vhostforce is set, as well.
Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Jason Wang <jasowang@redhat.com>
We use vhostforce to enable vhost even if Guests don't have MSI-X
support and we fall back to QEMU virtio-net.
This gives a very small performance gain, but the disadvantage
is that guest now controls which virtio code is running
(qemu or vhost) so our attack surface is doubled.
This patch will enable vhost unconditionally whenever it's requested.
For compatibility, enable vhost when vhostforce is set, as well.
Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Jason Wang <jasowang@redhat.com>