qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] dataplane: endian fix in host notification
Date: Thu, 25 Jun 2015 19:06:20 +0200	[thread overview]
Message-ID: <20150625190620.7403fb94@bahia.local> (raw)
In-Reply-To: <20150625183447.078473c3.cornelia.huck@de.ibm.com>

On Thu, 25 Jun 2015 18:34:47 +0200
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> On Thu, 25 Jun 2015 17:26:21 +0200
> Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> 
> > This field comes either LE with virtio 1.0, either guest endian with legacy.
> > It must only be accessed with an accessor that knows about the appropriate
> > endianness.
> > 
> > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > ---
> >  hw/virtio/dataplane/vring.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/hw/virtio/dataplane/vring.c b/hw/virtio/dataplane/vring.c
> > index 3fa421b9d773..a93ee2d338d7 100644
> > --- a/hw/virtio/dataplane/vring.c
> > +++ b/hw/virtio/dataplane/vring.c
> > @@ -117,7 +117,7 @@ void vring_disable_notification(VirtIODevice *vdev, Vring *vring)
> >  bool vring_enable_notification(VirtIODevice *vdev, Vring *vring)
> >  {
> >      if (virtio_has_feature(vdev, VIRTIO_RING_F_EVENT_IDX)) {
> > -        vring_avail_event(&vring->vr) = vring->vr.avail->idx;
> > +        vring_avail_event(&vring->vr) = vring_get_avail_idx(vdev, vring);
> >      } else {
> >          vring_clear_used_flags(vdev, vring, VRING_USED_F_NO_NOTIFY);
> >      }
> > 
> Hm... we should publish in the same endianness as the queue, shouldn't
> we? IOW, this seems fine.
> 
> OTOH, this prompted me to check for other places where we touch
> vring_avail_event and it seems to me that we need to convert
> vring->last_avail_idx before we set it in vring_pop().
> 
> I might be confused, though :)
> 

Heh you are the expert and it is more likely I am the confused one :)

But indeed, part of this confusion comes from these lines in vring_pop():

    if (virtio_has_feature(vdev, VIRTIO_RING_F_EVENT_IDX)) {
        vring_avail_event(&vring->vr) = vring->last_avail_idx;
    }

and the return statement in vring_disable_notification():

    return !vring_more_avail(vdev, vring);

i.e.

    return vring_get_avail_idx(vdev, vring) == vring->last_avail_idx;

which made me think last_avail_idx AND vring_avail_event(&vring->vr) have
host endianness... I will try what you suggest tomorrow.

Thanks for your feedback.

--
Greg

      parent reply	other threads:[~2015-06-25 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 15:26 [Qemu-devel] [PATCH] dataplane: endian fix in host notification Greg Kurz
2015-06-25 16:34 ` Cornelia Huck
2015-06-25 16:41   ` Cornelia Huck
2015-06-25 20:06     ` Greg Kurz
2015-06-25 17:06   ` Greg Kurz [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=20150625190620.7403fb94@bahia.local \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).