qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Shannon Zhao <zhaoshenglong@huawei.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 1/1] virtio: move host_features
Date: Tue, 26 May 2015 09:45:27 +0200	[thread overview]
Message-ID: <20150526094527.72ff1ce4.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <5564197A.4060803@huawei.com>

On Tue, 26 May 2015 14:58:02 +0800
Shannon Zhao <zhaoshenglong@huawei.com> wrote:

> 
> 
> On 2015/5/22 20:11, Cornelia Huck wrote:
> > Move host_features from the individual transport proxies into
> > the virtio device. Transports may continue to add feature bits
> > during device plugging.
> > 
> > This should it make easier to offer different sets of host features
> > for virtio-1/transitional support.
> > 
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> 
> Test virtio-mmio and virtio-pci. The host_features are same with/without
> this patch. There is a small comment on this below.
> 
> Tested-by: Shannon Zhao <shannon.zhao@linaro.org>
> 
> > ---
> >  hw/s390x/s390-virtio-bus.c     | 18 ++----------------
> >  hw/s390x/virtio-ccw.c          | 29 ++++++-----------------------
> >  hw/s390x/virtio-ccw.h          |  4 ----
> >  hw/virtio/virtio-bus.c         | 18 +++++-------------
> >  hw/virtio/virtio-mmio.c        | 22 +++-------------------
> >  hw/virtio/virtio-pci.c         | 17 ++++-------------
> >  hw/virtio/virtio.c             | 17 +++++++++--------
> >  include/hw/virtio/virtio-bus.h |  1 -
> >  include/hw/virtio/virtio.h     |  1 +
> >  9 files changed, 30 insertions(+), 97 deletions(-)

> > diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
> > index 10123f3..1817a07 100644
> > --- a/hw/virtio/virtio-mmio.c
> > +++ b/hw/virtio/virtio-mmio.c
> > @@ -80,7 +80,6 @@ typedef struct {
> >      SysBusDevice parent_obj;
> >      MemoryRegion iomem;
> >      qemu_irq irq;
> > -    uint32_t host_features;
> 
> Maybe we should delete host_features in PCI and s390 as well.

I thought I did, but probably missed them.

> 
> >      /* Guest accessible state needing migration and reset */
> >      uint32_t host_features_sel;
> >      uint32_t guest_features_sel;

Thanks for looking at this patch.

      reply	other threads:[~2015-05-26  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 12:11 [Qemu-devel] [PATCH RFC 0/1] virtio: host features in vdev Cornelia Huck
2015-05-22 12:11 ` [Qemu-devel] [PATCH RFC 1/1] virtio: move host_features Cornelia Huck
2015-05-26  6:58   ` Shannon Zhao
2015-05-26  7:45     ` Cornelia Huck [this message]

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=20150526094527.72ff1ce4.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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).