From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WhyL1-00022e-E9 for qemu-devel@nongnu.org; Wed, 07 May 2014 05:40:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WhyKu-0005nW-DE for qemu-devel@nongnu.org; Wed, 07 May 2014 05:40:31 -0400 Received: from mail-lb0-f181.google.com ([209.85.217.181]:34994) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WhyKu-0005nJ-71 for qemu-devel@nongnu.org; Wed, 07 May 2014 05:40:24 -0400 Received: by mail-lb0-f181.google.com with SMTP id u14so950872lbd.40 for ; Wed, 07 May 2014 02:40:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <01A509C3-B5E8-421E-8C12-E30A36AB1503@suse.de> References: <20140505074816.25523.71374.stgit@bahia.local> <20140505080520.25523.44406.stgit@bahia.local> <20140507101443.146fc26d@bahia.local> <5369F864.7040406@suse.de> <01A509C3-B5E8-421E-8C12-E30A36AB1503@suse.de> From: Peter Maydell Date: Wed, 7 May 2014 10:40:02 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Rusty Russell , QEMU Developers , "qemu-ppc@nongnu.org" , "bharata@linux.vnet.ibm.com" , =?UTF-8?Q?Andreas_F=C3=A4rber?= , Greg Kurz On 7 May 2014 10:37, Alexander Graf wrote: > > >> Am 07.05.2014 um 11:26 schrieb Peter Maydell : >> >>> On 7 May 2014 10:09, Alexander Graf wrote: >>> I don't think we should overengineer hacks for legacy virtio. >> >> Agreed. So what's our final conclusion: virtio endianness >> is the endianness of the guest kernel at the point where >> it triggers a reset of the virtio device, yes? > > The interrupt endianness for book3s PPC. Since that's an arch > specific thing I think we should just make the determination > mechanism arch dependent and list it in the spec. > > Booke for example would be vastly different since there is no > global LE flag - it's a bit in the TLB entries. Sure, but I think we should also state the general principle we're aiming to implement with the arch specific detail, so that people figuring out what a new arch should do have a guide to follow. thanks -- PMM