From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: openbios@openbios.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH] Enable support for PPC64 on qemu target v2
Date: Fri, 27 Feb 2009 22:03:01 +0200 [thread overview]
Message-ID: <f43fc5580902271203j1ff8312dvd4bcf36ab1ffd67e@mail.gmail.com> (raw)
In-Reply-To: <D3CC7C0C-401B-41F1-A8A4-E18CDF86A421@csgraf.de>
On 2/27/09, Alexander Graf <alex@csgraf.de> wrote:
> This patch enables OpenBIOS to initialize on PPC64, enabling support for
> -cpu 970fx.
> It gets up to the boot prompt and works rather good so far, though I haven't
> been able to run a kernel yet.
>
> For more recent PowerPC CPUs the PTE layout has changed, so we need to take
> that into account and create PTEs according to the new layout and at the new
> physical positions.
>
> v2 takes Laurent's comments into account
>
> Signed-off-by: Alexander Graf <alex@csgraf.de>
Great work. Just a minor nit:
+ vsid = (ea>>28) + SEGR_BASE;
Please add spaces around ">>".
I wonder if is_ppc64() is correct for all known CPUs. Alternatively
the CPU init function could set a global is_ppc64 flag, or call the
MMU initialize function.
In dsi_exception the mask could be initialized just once and in other
cases a static value could be used for speed. The speed of OpenBIOS is
of course not very critical.
next prev parent reply other threads:[~2009-02-27 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 23:39 [Qemu-devel] [PATCH] Enable support for PPC64 on qemu target v2 Alexander Graf
2009-02-27 0:25 ` Laurent Vivier
2009-02-27 20:03 ` Blue Swirl [this message]
2009-02-27 21:47 ` Blue Swirl
2009-02-28 0:24 ` Alexander Graf
2009-02-28 8:17 ` Blue Swirl
2009-02-27 22:24 ` Laurent Vivier
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=f43fc5580902271203j1ff8312dvd4bcf36ab1ffd67e@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=laurent@vivier.eu \
--cc=openbios@openbios.org \
--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).