From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60802) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxHQA-0006ey-7Z for qemu-devel@nongnu.org; Wed, 18 Jun 2014 11:05:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxHQ0-0008Mj-Vj for qemu-devel@nongnu.org; Wed, 18 Jun 2014 11:05:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36478) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxHQ0-0008MY-NV for qemu-devel@nongnu.org; Wed, 18 Jun 2014 11:04:56 -0400 Date: Wed, 18 Jun 2014 18:05:12 +0300 From: "Michael S. Tsirkin" Message-ID: <20140618150512.GC8370@redhat.com> References: <20140613111703.22108.14322.stgit@bahia.local> <20140617073631.GL16768@stefanha-thinkpad.redhat.com> <539FF0E3.6040407@suse.de> <20140618103814.GG14030@stefanha-thinkpad.redhat.com> <20140618134204.GB31764@redhat.com> <20140618162804.6e2cb399@bahia.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140618162804.6e2cb399@bahia.local> Subject: Re: [Qemu-devel] [PATCH v8 00/20] virtio endian-ambivalent target List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Greg Kurz Cc: Kevin Wolf , Peter Maydell , Anthony Liguori , Juan Quintela , Stefan Hajnoczi , Rusty Russell , Alexander Graf , QEMU Developers , "Aneesh Kumar K.V" , Stefan Hajnoczi , Amit Shah , Paolo Bonzini , Andreas =?iso-8859-1?Q?F=E4rber?= On Wed, Jun 18, 2014 at 04:28:04PM +0200, Greg Kurz wrote: > On Wed, 18 Jun 2014 16:42:04 +0300 > "Michael S. Tsirkin" wrote: > > On Wed, Jun 18, 2014 at 01:53:15PM +0100, Peter Maydell wrote: > > > On 18 June 2014 11:38, Stefan Hajnoczi 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. Not at all. I wouldn't invest the time in implementing this feature myself: I would just wait a bit and then work on backporting drivers instead. But you did and the patches are surprisingly clean. So I don't see a reason to keep them out of tree. > -- > 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.