From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: peter.maydell@linaro.org, mst@redhat.com,
peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
zhaoshenglong@huawei.com, pbonzini@redhat.com,
christoffer.dall@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/4] virtio: Move host features to backends
Date: Fri, 17 Apr 2015 15:43:35 +0200 [thread overview]
Message-ID: <20150417154335.7fa224ce.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1429272826-4145-1-git-send-email-shannon.zhao@linaro.org>
On Fri, 17 Apr 2015 20:13:42 +0800
Shannon Zhao <shannon.zhao@linaro.org> wrote:
[Some questions may be silly, but I'm not familiar with the virtio-mmio
code]
> The reason to do this is that the virtio-net-device can't expose host
> features to guest while using virtio-mmio. So the performance is low.
So how does virtio-mmio expose any host features?
>
> The virtio-*-pci, virtio-*-s390, and virtio-*-ccw already have the ability
> to forward property accesses to the backend child, by calling
> *_virtio_*_instance_init -> qdev_alias_all_properties.
Is there a way virtio-mmio could make use of instance_init?
>
> Here we move the host features to backends, involving
> DEFINE_VIRTIO_NET_FEATURES, DEFINE_VIRTIO_SCSI_FEATURES. So the virtio-mmio
> devices could have the host freatures, and this has a great performance
> improvement to virtio-mmio.
>
> This is also backward compatible for s390 and x86.
>
> Shannon Zhao (4):
> hw/s390x/virtio-ccw: Add virtio_ccw_device_plugged for virtio-ccw
> hw/s390x/s390-virtio-bus: Add virtio_s390_device_plugged for
> s390-virtio
> hw/net/virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net
> virtio-scsi: Move DEFINE_VIRTIO_SCSI_FEATURES to virtio-scsi
>
> hw/net/virtio-net.c | 4 ++++
> hw/s390x/s390-virtio-bus.c | 12 ++++++++++--
> hw/s390x/virtio-ccw.c | 13 +++++++++++--
> hw/scsi/virtio-scsi.c | 5 +++++
> hw/virtio/virtio-pci.c | 2 --
> include/hw/virtio/virtio-net.h | 1 +
> include/hw/virtio/virtio-scsi.h | 1 +
> 7 files changed, 32 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2015-04-17 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 12:13 [Qemu-devel] [PATCH 0/4] virtio: Move host features to backends Shannon Zhao
2015-04-17 12:13 ` [Qemu-devel] [PATCH 1/4] hw/s390x/virtio-ccw: Add virtio_ccw_device_plugged for virtio-ccw Shannon Zhao
2015-04-17 13:44 ` Cornelia Huck
2015-04-17 14:50 ` Shannon Zhao
2015-04-17 15:33 ` Peter Maydell
2015-04-18 1:36 ` Shannon Zhao
2015-04-17 12:13 ` [Qemu-devel] [PATCH 2/4] hw/s390x/s390-virtio-bus: Add virtio_s390_device_plugged for s390-virtio Shannon Zhao
2015-04-17 12:13 ` [Qemu-devel] [PATCH 3/4] hw/net/virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net Shannon Zhao
2015-04-17 14:05 ` Peter Maydell
2015-04-17 14:50 ` Shannon Zhao
2015-04-17 15:03 ` Peter Maydell
2015-04-17 12:13 ` [Qemu-devel] [PATCH 4/4] virtio-scsi: Move DEFINE_VIRTIO_SCSI_FEATURES to virtio-scsi Shannon Zhao
2015-04-17 13:43 ` Cornelia Huck [this message]
2015-04-17 14:00 ` [Qemu-devel] [PATCH 0/4] virtio: Move host features to backends Peter Maydell
2015-04-20 8:54 ` Cornelia Huck
2015-04-20 9:02 ` Peter Maydell
2015-04-20 9:12 ` Michael S. Tsirkin
2015-04-20 12:14 ` Cornelia Huck
2015-04-20 12:43 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150417154335.7fa224ce.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=zhaoshenglong@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).