On 12/3/18 9:32 AM, Paolo Bonzini wrote:
There is no reason for CONFIG_VHOST_NET to be specific to a single target; it is a host feature that can be add to all targets, as long as they support
s/add/added/
the virtio-net device. Currently CONFIG_VHOST_NET depends on CONFIG_KVM, but ioeventfd support is present in the core memory API and works with other accelerators as well. As a first step, move the vhost-net stubs to a separate file. Later, they will become conditional on CONFIG_VIRTIO_NET, which is not available in .c files. Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com> Signed-off-by: Paolo Bonzini <pbonz...@redhat.com> --- hw/net/Makefile.objs | 4 ++- hw/net/vhost_net-stub.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++ hw/net/vhost_net.c | 74 -------------------------------------- 3 files changed, 98 insertions(+), 75 deletions(-) create mode 100644 hw/net/vhost_net-stub.c
-- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
