virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net
commitda3e8a23492dbc13c4b70d90b6ae42970624e63a
authorShannon Zhao <shannon.zhao@linaro.org>
Tue, 28 Apr 2015 11:51:12 +0000 (28 19:51 +0800)
committerMichael S. Tsirkin <mst@redhat.com>
Tue, 28 Apr 2015 15:44:39 +0000 (28 17:44 +0200)
treef00eaa60c8884b59beaff014131c9db111d27b89
parent51f7cb974ba1af9f68302f2bae4bf0161fb0ab03
virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net

So far virtio-net-device can't expose host features to guest while
using virtio-mmio because it doesn't set DEFINE_VIRTIO_NET_FEATURES on
backend or transport. So the performance is low.

The host features belong to the backend while virtio-net-pci,
virtio-net-s390 and virtio-net-ccw set the DEFINE_VIRTIO_NET_FEATURES
on transports. But they already have the ability to forward property
accesses to the backend child. So if we move the host features to
backends, it doesn't break the backwards compatibility for them and
make host features work while using virtio-mmio.

Here we move DEFINE_VIRTIO_NET_FEATURES to the backend virtio-net. The
transports just sync the host features from backend. Meanwhile move
virtio_net_set_config_size to virtio-net to make sure the config size
is correct and don't expose it.

Signed-off-by: Shannon Zhao <zhaoshenglong@huawei.com>
Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
hw/net/virtio-net.c
hw/s390x/s390-virtio-bus.c
hw/s390x/virtio-ccw.c
hw/virtio/virtio-pci.c
include/hw/virtio/virtio-net.h