From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [patch 32/43] lguest: Virtio interface Date: Fri, 12 Oct 2007 00:17:13 +1000 Message-ID: <200710120017.13725.rusty@rustcorp.com.au> References: <20070926063618.956228976@rustcorp.com.au> <20070926063650.895058914@rustcorp.com.au> <200710101050.49012.borntraeger@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200710101050.49012.borntraeger@de.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: virtualization@lists.linux-foundation.org Cc: Christian Borntraeger List-Id: virtualization@lists.linuxfoundation.org On Wednesday 10 October 2007 18:50:48 Christian Borntraeger wrote: > Hi Rusty, > > I have a late question :-) > > > There is also a generic implementation of config space which drivers can > > query to get setup information from the host. > > After thinking about that for a while, is there a special reason the config > field is defined as little endian? The only reason I can come up with, is > to use virtio for cross platform emulators, lets say a ppc emulates an x86 > system with virtio devices instead of real ones. > > Do you have other reasons for a fixed endianess? Other people came up with really good reasons, but in fact it was because PCI is little-endian. If someone found a compelling counter-argument, I'd change it. Cheers, Rusty.