From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] dataplane: drop copy_in_vring_desc()
Date: Fri, 26 Jun 2015 14:11:12 +0200 [thread overview]
Message-ID: <20150626141112.7a92aa82@bahia.local> (raw)
In-Reply-To: <20150626100045.GJ15457@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Fri, 26 Jun 2015 11:00:45 +0100
Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Thu, Jun 25, 2015 at 05:26:09PM +0200, Greg Kurz wrote:
> > During early virtio 1.0 devel, there were several proposals about how to
> > deal 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 cross-endian setups with the following 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 gives a smaller patch.
>
> Cornelia already sent "[PATCH] Revert "dataplane: allow virtio-1
> devices" to revert f5a5628cf0b. I acked it but the patch is going
> through Michael Tsirkin.
Indeed... my bad, I overlooked that thread...
--
G
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-06-26 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 15:26 [Qemu-devel] [PATCH] dataplane: drop copy_in_vring_desc() Greg Kurz
2015-06-26 10:00 ` Stefan Hajnoczi
2015-06-26 12:11 ` 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=20150626141112.7a92aa82@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@gmail.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).