From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVtS6-0007iH-BJ for qemu-devel@nongnu.org; Fri, 15 Jan 2010 16:11:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVtS1-0007i2-UD for qemu-devel@nongnu.org; Fri, 15 Jan 2010 16:11:29 -0500 Received: from [199.232.76.173] (port=55365 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVtS1-0007hz-On for qemu-devel@nongnu.org; Fri, 15 Jan 2010 16:11:25 -0500 Received: from mail-yw0-f176.google.com ([209.85.211.176]:35625) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NVtS1-0001Eb-4v for qemu-devel@nongnu.org; Fri, 15 Jan 2010 16:11:25 -0500 Received: by ywh6 with SMTP id 6so896957ywh.4 for ; Fri, 15 Jan 2010 13:11:24 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1263581172-16129-1-git-send-email-atar4qemu@google.com> From: Artyom Tarasenko Date: Fri, 15 Jan 2010 22:11:04 +0100 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: sparc32 do_unassigned_access overhaul List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org 2010/1/15 Blue Swirl : > On Fri, Jan 15, 2010 at 6:46 PM, Artyom Tarasenko > wrote: >> According to pages 9-31 - 9-34 of "SuperSPARC & MultiCache Controller >> User's Manual": >> >> 1. "A lower priority fault may not overwrite the >> =A0 =A0MFSR status of a higher priority fault." >> 2. The MFAR is overwritten according to the policy defined for the MFSR >> 3. The overwrite bit is asserted if the fault status register (MFSR) >> =A0 has been written more than once by faults of the same class >> 4. SuperSPARC will never place instruction fault addresses in the MFAR. >> >> Implementation of points 1-3 allows booting Solaris 2.6 and 2.5.1. > > Nice work! This also passes my tests. I'm afraid we still are not there yet though: Solaris 7 fails potentially d= ue to another bug in the MMU emulation, and the initial [missing-] RAM detection in OBP fails very probably due to a bug in in the MMU emulation. > However, there are some CODING_STYLE issues. Is it something you do by hand (or, actually, by eyes), or is there a way I can automatically test my patches before sending? --=20 Regards, Artyom Tarasenko solaris/sparc under qemu blog: http://tyom.blogspot.com/