From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53927) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvps0-0003vb-Og for qemu-devel@nongnu.org; Fri, 10 Feb 2012 07:46:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rvprz-0007cU-D3 for qemu-devel@nongnu.org; Fri, 10 Feb 2012 07:46:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55355) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvprz-0007cE-28 for qemu-devel@nongnu.org; Fri, 10 Feb 2012 07:46:31 -0500 Message-ID: <4F35119C.3030404@redhat.com> Date: Fri, 10 Feb 2012 13:46:20 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1326731457-9056-1-git-send-email-pbonzini@redhat.com> <1326731457-9056-12-git-send-email-pbonzini@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 11/15] virtio-scsi: Add virtio-scsi stub device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org, Stefan Hajnoczi On 02/10/2012 01:41 PM, Stefan Hajnoczi wrote: > At this early stage we still have the option of designing the device > to be little- or big-endian. I'm in favour of a fixed endianness even > though existing virtio devices tend to use guest-endian. > > What do you think? Interesting idea, but I'd say no for three reasons: 1) The virtqueue would remain in guest-endianness. 2) Even if the result is better, it is still different from every other device, so right now it would be a one-off exception (and it would likely remain so; it's not like there are new virtio devices every week :)). 3) I'm afraid of breaking something else, for example pSeries virtio is doing complicated things that I don't really understand to split the I/O BAR in two parts, the first in PCI endianness and the second in native endianness. Paolo