From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Anthony Liguori" <aliguori@amazon.com>,
"Juan Quintela" <quintela@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Alexander Graf" <agraf@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Amit Shah" <amit.shah@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v8 00/20] virtio endian-ambivalent target
Date: Wed, 18 Jun 2014 16:28:04 +0200 [thread overview]
Message-ID: <20140618162804.6e2cb399@bahia.local> (raw)
In-Reply-To: <20140618134204.GB31764@redhat.com>
On Wed, 18 Jun 2014 16:42:04 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote:
> > On 18 June 2014 11:38, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > > What bothers me is that real hardware can't do this.
> >
> > Real hardware doesn't have "endianness matches guest CPU endianness"
> > semantics, which is what the virtio spec mandates...
>
> So it was buggy. We never thought anyone would do a cross endian CPU :(.
> We are fixing it in 1.0.
>
virtio isn't the only victim... we also have vga. The problem can pop up
anywhere you rely on TARGET_WORDS_BIGENDIAN.
> > > Given that VIRTIO
> > > 1.0 is always little-endian I guess this is just a temporary hack for
> > > ppc little-endian. Would be nice to add a comment so it's clear why
> > > this approach is being taken instead of a cleaner solution.
> >
> > Also for ARM big-endian, and indeed for any CPU with runtime
> > configurable endianness that wants to use the kernel virtio
> > drivers that exist in the real world rather than the theoretical
> > future ones that might some day be written for the 1.0 virtio
> > spec...
> >
> > thanks
> > -- PMM
>
> That's not a theoretical future.
> Spec will almost certainly be frozen two weeks from now.
> So it is almost certain that drivers will be there in 3.17.
>
I don't want argue on the dates but I doubt that all legacy users
will switch to 1.0 as soon as it shows up... a transition period
may be needed.
> Existing distros can then simply backport the
> drivers - same as they would with any other new hardware.
>
Are you saying that upstream QEMU should not to support the
transition between legacy and 1.0 at all ?
Cheers.
--
Gregory Kurz kurzgreg@fr.ibm.com
gkurz@linux.vnet.ibm.com
Software Engineer @ IBM/Meiosys http://www.ibm.com
Tel +33 (0)562 165 496
"Anarchy is about taking complete responsibility for yourself."
Alan Moore.
next prev parent reply other threads:[~2014-06-18 14:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 11:18 [Qemu-devel] [PATCH v8 00/20] virtio endian-ambivalent target Greg Kurz
2014-06-13 11:18 ` [Qemu-devel] [PATCH v8 01/20] virtio-serial: don't migrate the config space Greg Kurz
2014-06-13 11:33 ` Alexander Graf
2014-06-19 10:40 ` Amit Shah
2014-06-19 11:17 ` Greg Kurz
2014-06-19 11:32 ` Michael S. Tsirkin
2014-06-13 11:19 ` [Qemu-devel] [PATCH v8 02/20] virtio: introduce device specific migration calls Greg Kurz
2014-06-13 11:19 ` [Qemu-devel] [PATCH v8 03/20] virtio-net: implement per-device " Greg Kurz
2014-06-13 11:19 ` [Qemu-devel] [PATCH v8 04/20] virtio-blk: " Greg Kurz
2014-06-13 11:20 ` [Qemu-devel] [PATCH v8 05/20] virtio-serial: " Greg Kurz
2014-06-13 11:20 ` [Qemu-devel] [PATCH v8 06/20] virtio-balloon: " Greg Kurz
2014-06-13 11:21 ` [Qemu-devel] [PATCH v8 07/20] virtio-rng: " Greg Kurz
2014-06-13 11:21 ` [Qemu-devel] [PATCH v8 08/20] virtio: add subsections to the migration stream Greg Kurz
2014-06-13 11:21 ` [Qemu-devel] [PATCH v8 09/20] exec: introduce target_words_bigendian() helper Greg Kurz
2014-06-13 11:41 ` Alexander Graf
2014-06-13 12:05 ` Greg Kurz
2014-06-13 11:22 ` [Qemu-devel] [PATCH v8 10/20] cpu: introduce CPUClass::virtio_is_big_endian() Greg Kurz
2014-06-13 11:42 ` Alexander Graf
2014-06-13 12:08 ` Greg Kurz
2014-06-13 11:23 ` [Qemu-devel] [PATCH v8 11/20] virtio: add endian-ambivalent support to VirtIODevice Greg Kurz
2014-06-13 11:46 ` Alexander Graf
2014-06-13 12:14 ` Greg Kurz
2014-06-13 12:41 ` Alexander Graf
2014-06-13 12:52 ` Greg Kurz
2014-06-13 11:23 ` [Qemu-devel] [PATCH v8 12/20] virtio: memory accessors for endian-ambivalent targets Greg Kurz
2014-06-13 11:24 ` [Qemu-devel] [PATCH v8 13/20] virtio: allow byte swapping for vring Greg Kurz
2014-06-13 11:24 ` [Qemu-devel] [PATCH v8 14/20] virtio-net: use virtio wrappers to access headers Greg Kurz
2014-06-13 11:52 ` Alexander Graf
2014-06-13 12:24 ` Cedric Le Goater
2014-06-13 12:40 ` Greg Kurz
2014-06-13 11:24 ` [Qemu-devel] [PATCH v8 15/20] virtio-balloon: use virtio wrappers to access page frame numbers Greg Kurz
2014-06-13 11:24 ` [Qemu-devel] [PATCH v8 16/20] virtio-blk: use virtio wrappers to access headers Greg Kurz
2014-06-13 11:24 ` [Qemu-devel] [PATCH v8 17/20] virtio-scsi: " Greg Kurz
2014-06-19 15:05 ` Greg Kurz
2014-06-20 8:24 ` Paolo Bonzini
2014-06-20 8:33 ` Greg Kurz
2014-06-13 11:25 ` [Qemu-devel] [PATCH v8 18/20] virtio-serial-bus: " Greg Kurz
2014-06-13 11:25 ` [Qemu-devel] [PATCH v8 19/20] virtio-9p: " Greg Kurz
2014-06-13 11:26 ` [Qemu-devel] [PATCH v8 20/20] target-ppc: enable virtio endian ambivalent support Greg Kurz
2014-06-13 11:56 ` [Qemu-devel] [PATCH v8 00/20] virtio endian-ambivalent target Alexander Graf
2014-06-16 15:07 ` Greg Kurz
2014-06-16 16:53 ` Amit Shah
2014-06-17 7:36 ` Stefan Hajnoczi
2014-06-17 7:40 ` Alexander Graf
2014-06-18 10:38 ` Stefan Hajnoczi
2014-06-18 12:35 ` Greg Kurz
2014-06-18 15:12 ` Michael S. Tsirkin
2014-06-18 15:14 ` Alexander Graf
2014-06-18 15:26 ` Michael S. Tsirkin
2014-06-19 9:51 ` Stefan Hajnoczi
2014-06-18 12:53 ` Peter Maydell
2014-06-18 13:42 ` Michael S. Tsirkin
2014-06-18 14:28 ` Greg Kurz [this message]
2014-06-18 15:05 ` Michael S. Tsirkin
2014-06-18 15:35 ` Peter Maydell
2014-06-18 15:37 ` Alexander Graf
2014-06-18 15:40 ` Peter Maydell
2014-06-18 15:41 ` Alexander Graf
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=20140618162804.6e2cb399@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=amit.shah@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@gmail.com \
--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).