From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48491) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uyja1-0006dL-PM for qemu-devel@nongnu.org; Mon, 15 Jul 2013 10:16:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uyja0-00030o-Ix for qemu-devel@nongnu.org; Mon, 15 Jul 2013 10:16:45 -0400 Message-ID: <1373897779.19894.351.camel@pasglop> From: Benjamin Herrenschmidt Date: Tue, 16 Jul 2013 00:16:19 +1000 In-Reply-To: <87sizfudli.fsf@codemonkey.ws> References: <51C75FA6.6080903@reactos.org> <51C7E21A.9090005@web.de> <8A36D64D-0625-49E1-9E59-391DAEEBD1FC@suse.de> <51DEA91B.40903@suse.de> <3FAA7DE1-06A0-45C5-885C-0433BCC0CFE8@suse.de> <5D205309-1154-4730-902E-BF07F5D3B4EB@suse.de> <1373581960.19894.109.camel@pasglop> <02433CA4-954D-4C56-A4A4-7BC0D62638C0@suse.de> <1373628932.19894.158.camel@pasglop> <878v1bvfaw.fsf@codemonkey.ws> <1373669427.19894.202.camel@pasglop> <87sizfudli.fsf@codemonkey.ws> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v3 11/14] ioport: Switch dispatching to memory core layer List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Peter Maydell , Liu Ping Fan , Alexander Graf , qemu-devel Developers , "qemu-ppc@nongnu.org list:PowerPC" , Paolo Bonzini , Jan Kiszka , Andreas =?ISO-8859-1?Q?F=E4rber?= , =?ISO-8859-1?Q?Herv=E9?= Poussineau On Mon, 2013-07-15 at 09:01 -0500, Anthony Liguori wrote: > On PPC, le_mode only really affects load/stores and instruction > decoding. Any shared data structures between the CPU and OS remain big > endian. Translation: On ppc with the specific machine type "pseries" which emulates a paravirtualized environment, the data structures between the guest and the hypervisor remain big endian :-) But this is essentially irrelevant to the basic discussion about endian handling (ie. PCI devices remain LE, etc...). Point is, TCG can deal with dual endian reasonably easily. The main issues are around things like virtio with its stupid concept of "guest endian" (wtf does guest endian means on a dual endian processor ?) but I think we've whacked Rusty's head plenty enough on that one... and it's not that hard to work around. > So TARGET_WORDS_BIGENDIAN is still accurate even when le_mode=1. It's > not the semantic equivalent of changing TARGET_WORDS. The point is that it's unnecessary :-) IE. We should aim to get rid of the concept of target endianness altogether :-) Cheers, Ben.