From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SdNdk-00026R-1G for qemu-devel@nongnu.org; Sat, 09 Jun 2012 11:31:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SdNdh-0008J4-Vl for qemu-devel@nongnu.org; Sat, 09 Jun 2012 11:31:47 -0400 Received: from cantor2.suse.de ([195.135.220.15]:59629 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SdNdh-0008IU-PW for qemu-devel@nongnu.org; Sat, 09 Jun 2012 11:31:45 -0400 Message-ID: <4FD36C5B.6020103@suse.de> Date: Sat, 09 Jun 2012 17:31:39 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1339206871-4706-1-git-send-email-afaerber@suse.de> <20120609152003.GA5062@zapo> In-Reply-To: <20120609152003.GA5062@zapo> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 0/3] xilinx: Speed up the build List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Edgar E. Iglesias" Cc: "Peter A. G. Crosthwaite" , qemu-devel@nongnu.org, Alexander Graf , Blue Swirl , Avi Kivity , Paolo Bonzini Am 09.06.2012 17:20, schrieb Edgar E. Iglesias: > On Sat, Jun 09, 2012 at 03:54:28AM +0200, Andreas F=E4rber wrote: >> xilinx_ethlite.c uses tswap32(). Have you ever tested this device to w= ork on >> microblazeel? I wonder if we could change the device from DEVICE_NATIV= E_ENDIAN >> to DEVICE_BIG_ENDIAN and in place of tswap32() use a bswap32() conditi= onal on >> HOST_WORDS_BIGENDIAN so that it becomes independent of the target, too= ? >=20 > I don't think that will work. the swap is needed if the endianness of t= he host > is different from the one of the target... My thinking was: If we can force the device endianness to a known value then only the host endianness (not the target endianness) matters because the Memory API will take care of the device endianness. The question is: Is the device LE for microblazeel or is it always BE? > IIRC, the issue is that the device has a built-in RAM mapped so close t= o > the regs that they end up in the same "page". With Avis memory-api mayb= e it's > possible to expose this sub-page area as a memory? Me and Avi fixed some bugs for subpage areas, it should work in theory (for TCG/qtest). Not being aware of a MicroBlaze KVM, if it's a RAM region then we should definitely model it as such. Cheers, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg