From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LdRRb-0007Ib-JG for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:49:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LdRRZ-0007Hu-2Y for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:49:38 -0500 Received: from [199.232.76.173] (port=57290 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LdRRY-0007Hr-Vq for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:49:37 -0500 Received: from mail-bw0-f171.google.com ([209.85.218.171]:46625) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LdRRY-0004q1-DB for qemu-devel@nongnu.org; Sat, 28 Feb 2009 10:49:36 -0500 Received: by bwz19 with SMTP id 19so1306441bwz.34 for ; Sat, 28 Feb 2009 07:49:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <29ACB5AD-64D9-4D83-B0E8-A111A919D0F2@csgraf.de> References: <1235832403-29902-1-git-send-email-agraf@suse.de> <29ACB5AD-64D9-4D83-B0E8-A111A919D0F2@csgraf.de> Date: Sat, 28 Feb 2009 17:49:34 +0200 Message-ID: Subject: Re: [Qemu-devel] [PATCH] PPC: Use correct values for 970 interrupts and hreset From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel@nongnu.org On 2/28/09, Alexander Graf wrote: > > On 28.02.2009, at 16:21, Blue Swirl wrote: > > > > On 2/28/09, Alexander Graf wrote: > > > > > The 970 doesn't set exception prefix values by default. According to > > > the ISA it just jumps to real mode with nip=3Dvector. > > > > > > Because of that the current hreset_vector is rendered invalid. Before= , > > > it would go to excp_prefix (ROM base) + 0x100 (reset vector) and get > > > into the firmware. > > > > > > But with the corrected excp_prefix, we now have to jump to the real > > > entry point, which is at 0xFFFFFFFC. > > > > > > > I don't think this is correct. 970FX uses HIOR to specify the > > exception vector base, please see "IBM PowerPC 970FX RISC > > Microprocessor", page 273. > > > > Oh I think I know what you're saying: > > The Hardware Interrupt Offset register, HIOR should be scanned (the HIOR= is > on the mode ring) to the > system=E2=80=99s starting address during initialization. Subsequently HI= OR should > be set to zero. > > That basically means, HIOR is 0xfff00000 on bootup, but magically become= s 0 > at - eh - a random point in time? Or should the firmware set it? How is t= his > implemented on a G5 that doesn't know LPAR features, like Apple's G5? Firmware should clear it. Maybe their BIOS sets all unknown SPRs to 0?