From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxFN6-0007BB-Q4 for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:53:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxFMv-0002m7-Gy for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:53:48 -0400 Received: from mail-lb0-f173.google.com ([209.85.217.173]:62020) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxFMv-0002is-AI for qemu-devel@nongnu.org; Wed, 18 Jun 2014 08:53:37 -0400 Received: by mail-lb0-f173.google.com with SMTP id s7so480990lbd.4 for ; Wed, 18 Jun 2014 05:53:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140618103814.GG14030@stefanha-thinkpad.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> From: Peter Maydell Date: Wed, 18 Jun 2014 13:53:15 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 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: Stefan Hajnoczi Cc: Kevin Wolf , Anthony Liguori , "Michael S. Tsirkin" , Rusty Russell , Alexander Graf , QEMU Developers , Juan Quintela , "Aneesh Kumar K.V" , Stefan Hajnoczi , Amit Shah , Paolo Bonzini , =?UTF-8?Q?Andreas_F=C3=A4rber?= , Greg Kurz 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... > 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