qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Alexander Graf <alex@csgraf.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PPC: Use correct values for 970 interrupts and hreset
Date: Sat, 28 Feb 2009 17:49:34 +0200	[thread overview]
Message-ID: <f43fc5580902280749w7fe1a393ka9c8e54f68d7b9b2@mail.gmail.com> (raw)
In-Reply-To: <29ACB5AD-64D9-4D83-B0E8-A111A919D0F2@csgraf.de>

On 2/28/09, Alexander Graf <alex@csgraf.de> wrote:
>
>  On 28.02.2009, at 16:21, Blue Swirl wrote:
>
>
> > On 2/28/09, Alexander Graf <agraf@suse.de> wrote:
> >
> > > The 970 doesn't set exception prefix values by default. According to
> > > the ISA it just jumps to real mode with nip=vector.
> > >
> > > 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’s starting address during initialization. Subsequently HIOR should
> be set to zero.
>
>  That basically means, HIOR is 0xfff00000 on bootup, but magically becomes 0
> at - eh - a random point in time? Or should the firmware set it? How is this
> 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?

      reply	other threads:[~2009-02-28 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 14:46 [Qemu-devel] [PATCH] PPC: Use correct values for 970 interrupts and hreset Alexander Graf
2009-02-28 15:21 ` Blue Swirl
2009-02-28 15:27   ` Alexander Graf
2009-02-28 15:32   ` Alexander Graf
2009-02-28 15:49     ` Blue Swirl [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f43fc5580902280749w7fe1a393ka9c8e54f68d7b9b2@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=alex@csgraf.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).