From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HI7eW-0006hy-1X for qemu-devel@nongnu.org; Fri, 16 Feb 2007 13:17:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HI7eU-0006hY-N9 for qemu-devel@nongnu.org; Fri, 16 Feb 2007 13:17:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HI7eU-0006hV-I1 for qemu-devel@nongnu.org; Fri, 16 Feb 2007 13:17:46 -0500 Received: from nf-out-0910.google.com ([64.233.182.190]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HI7eU-00027a-4H for qemu-devel@nongnu.org; Fri, 16 Feb 2007 13:17:46 -0500 Received: by nf-out-0910.google.com with SMTP id x30so1486070nfb for ; Fri, 16 Feb 2007 10:17:45 -0800 (PST) Message-ID: Date: Fri, 16 Feb 2007 13:17:45 -0500 From: Peter Sender: pjcreath@gmail.com Subject: Re: [Qemu-devel] Potential sparc32 MMU bug In-Reply-To: <200702161701.59960.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200702161701.59960.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org It definitely gets blocked by something: if I leave the the trap table in the .text section, the write silently fails. If I move the trap table to the .data section, the write succeeds. If I move the trap table over to .rodata, the write fails again. What are you looking at that suggests the whole sparc bios is loaded read/write? On 2/16/07, Paul Brook wrote: > On Friday 16 February 2007 16:55, Peter wrote: > > While working on getting SunOS to boot under qemu, I ran into a very > > odd bug, and I'm not sure whose fault it is. > > > > The SunOS bootloader tries to install trap 0 by writing to the trap > > table. The trap table is in the .text (read-only) section of the > > OpenBIOS ROM. > > I don't know about sparc, but it's normal for writes to ROM to be ignored. > However by my reading the sparc bios is loaded into RAM anyway, so it > shouldn't matter. > > Paul >