From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46967) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9ihj-0008Cy-GJ for qemu-devel@nongnu.org; Thu, 06 Sep 2012 16:29:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T9ihi-0008Pe-JU for qemu-devel@nongnu.org; Thu, 06 Sep 2012 16:29:35 -0400 Received: from mail-vb0-f45.google.com ([209.85.212.45]:33317) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9ihi-0008Pa-F9 for qemu-devel@nongnu.org; Thu, 06 Sep 2012 16:29:34 -0400 Received: by vbip1 with SMTP id p1so1833142vbi.4 for ; Thu, 06 Sep 2012 13:29:33 -0700 (PDT) Sender: Richard Henderson Message-ID: <504907AA.5080505@twiddle.net> Date: Thu, 06 Sep 2012 13:29:30 -0700 From: Richard Henderson MIME-Version: 1.0 References: <5955be78eb92f05b5fafa58477c543f89afaf39c.1346606812.git.blauwirbel@gmail.com> <50464BA2.5070209@twiddle.net> <50467A9C.9040104@twiddle.net> <28349C5D-BE03-4D8C-A524-0719ADFDBC47@suse.de> <504770F0.5040104@twiddle.net> <0CA76405-815A-40FF-9716-C1DAD1B71DBC@suse.de> In-Reply-To: <0CA76405-815A-40FF-9716-C1DAD1B71DBC@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 02/21] target-s390x: split FPU ops List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Blue Swirl , qemu-devel@nongnu.org On 09/06/2012 11:42 AM, Alexander Graf wrote: > Richard, while at it, could you please check the s390x tcg target? > Running any target on there seems to break in the TLB code for me. I did successfully run a simple linux-user test directly off blue's patch set. It exercised a bit of fp and system calls (printf). I don't have a system environment set up at the moment... > I'm mostly surprised by the env value. Why is that a 32-bit pointer? It depends on where objects get loaded in memory of course. I don't think there's anything particularly surprising about an object loaded into the load 32-bits. That mmu_idx on the other hand... one begins to wonder if the debugger is actually lying to you. r~