From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] dataplane: drop copy_in_vring_desc()
Date: Fri, 26 Jun 2015 19:05:07 +0200 [thread overview]
Message-ID: <20150626190507.3fb83338@bahia.local> (raw)
In-Reply-To: <20150626182809-mutt-send-email-mst@redhat.com>
On Fri, 26 Jun 2015 18:28:42 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Jun 26, 2015 at 02:18:38PM +0200, Greg Kurz wrote:
> > On Fri, 26 Jun 2015 12:28:45 +0200
> > Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> >
> > > On Fri, 26 Jun 2015 09:32:21 +0200
> > > Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> > >
> > > > During early virtio 1.0 devel, there were several proposals about how to
> > > > deal with the endianness of the vring descriptor fields:
> > > > - convert the decriptor to host endianness in a single place, and use its
> > > > fields directly in the code
> > > > - keep the descriptor untouched and use virtio memory helpers to access its
> > > > fields with the appropriate endianness
> > > >
> > > > It seems like both approaches got merged: commit f5a5628cf0b6 introduces
> > > > an extra swap that negates the one brought by commit b0e5d90ebc3e. This
> > > > breaks boot in SLOF (BE client) when host is ppc64le with the following
> > > > QEMU error:
> > > >
> > > > Failed to map descriptor addr 0x18e2517e00000000 len 268435456
> > > >
> > > > A solution could be to revert f5a5628cf0b6, but dropping copy_in_vring_desc()
> > > > is equivalent and result in a smaller patch.
> > >
> > > I'd prefer the revert, as the resulting code is nicer IMHO.
> > >
> >
> > Agreed. It is good to clear the endianness noise out of the real code. :)
>
> Can you please send v2 that works the way you want it?
>
Taken from a previous mail by Stefan:
"Cornelia already sent "[PATCH] Revert "dataplane: allow virtio-1
devices" to revert f5a5628cf0b. I acked it but the patch is going
through Michael Tsirkin."
I guess you just have to take Cornelia's patch + Stefan's ack,
and patch 2/2 in my series + Cornelia's rb, and we are all set. :)
FWIW I tested and it works exactly the same.
> > > But your second patch should apply regardless.
> > >
> >
> > Thanks for your feedback.
> >
> > > >
> > > > This patch allows SLOF to boot the OS.
> > > >
> > > > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > > > ---
> > > > hw/virtio/dataplane/vring.c | 14 ++------------
> > > > 1 file changed, 2 insertions(+), 12 deletions(-)
>
next prev parent reply other threads:[~2015-06-26 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 7:32 [Qemu-devel] [PATCH 0/2] dataplane: cross-endian fixes Greg Kurz
2015-06-26 7:32 ` [Qemu-devel] [PATCH 1/2] dataplane: drop copy_in_vring_desc() Greg Kurz
2015-06-26 10:28 ` Cornelia Huck
2015-06-26 12:18 ` Greg Kurz
2015-06-26 16:28 ` Michael S. Tsirkin
2015-06-26 17:05 ` Greg Kurz [this message]
2015-06-28 13:03 ` Michael S. Tsirkin
2015-06-28 21:49 ` Greg Kurz
2015-06-29 8:20 ` Greg Kurz
2015-06-26 7:32 ` [Qemu-devel] [PATCH 2/2] dataplane: fix cross-endian issues Greg Kurz
2015-06-26 10:37 ` Cornelia Huck
2015-06-26 10:15 ` [Qemu-devel] [PATCH 0/2] dataplane: cross-endian fixes Stefan Hajnoczi
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=20150626190507.3fb83338@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).