From: Hollis Blanchard <hollisb@us.ibm.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, kvm-ppc@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 3/4] PowerPC 440EP SoC emulation
Date: Tue, 16 Dec 2008 09:37:58 -0600 [thread overview]
Message-ID: <1229441878.31337.35.camel@localhost.localdomain> (raw)
In-Reply-To: <20081216104556.GB20364@volta.aurel32.net>
On Tue, 2008-12-16 at 11:45 +0100, Aurelien Jarno wrote:
> On Mon, Dec 15, 2008 at 06:17:31PM -0600, Hollis Blanchard wrote:
> > Wire up the system-on-chip devices present on 440EP chips.
> >
> > This patch is a little unusual in that qemu doesn't actually emulate the 440
> > core, but we use this board code with KVM (which does). If/when 440 core
> > emulation is supported, the kvm_enabled() hack can be removed.
> >
>
> What are the mains differences between 405 and 440 cores? Would it be
> easy to add support for 440 core in QEMU?
It's been a while since I programmed for the 405, but from memory:
Unlike the 405, the 440 is a Book E core. The biggest difference is that
there is no real mode; MMU translation is always active. MSR[IR] and DR
have been replaced with IS and DS, and those "address space" bits
contribute to the 41-bit virtual address (32-bit effective, 8-bit PID
like 405, 1-bit AS). The TLB organization is pretty much the same as 405
(64-entry fully associative), though the data in each entry has changed
a little.
Fixed interrupt vectors have been replaced with programmable ones, via
the IVPR base register and 16 IVOR registers, indicating the offset of
each vector from IVPR.
There is a Application Note that more fully lists the software
differences:
https://www.amcc.com/MyAMCC/retrieveDocument/PowerPC/440GP/PPC440GP_AN2020_SWC405GP.pdf
Because the MMU is always on, tlbia doesn't exist any more. There are a
few other minor instruction and register changes.
As I've mentioned, most 440 peripherals are the same or similar to 405,
which is definitely helpful.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-12-16 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 0:17 [Qemu-devel] KVM PowerPC support v3 Hollis Blanchard
2008-12-16 0:17 ` [Qemu-devel] [PATCH 1/4] Implement device tree support needed for Bamboo emulation Hollis Blanchard
2008-12-16 0:17 ` [Qemu-devel] [PATCH 2/4] Enable KVM for ppcemb Hollis Blanchard
2008-12-16 0:17 ` [Qemu-devel] [PATCH 3/4] PowerPC 440EP SoC emulation Hollis Blanchard
2008-12-16 10:45 ` Aurelien Jarno
2008-12-16 15:37 ` Hollis Blanchard [this message]
2008-12-16 0:17 ` [Qemu-devel] [PATCH 4/4] IBM PowerPC 440EP Bamboo reference board emulation Hollis Blanchard
2008-12-16 10:47 ` Aurelien Jarno
2008-12-16 15:14 ` Hollis Blanchard
2008-12-16 10:44 ` [Qemu-devel] KVM PowerPC support v3 Aurelien Jarno
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=1229441878.31337.35.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=aurelien@aurel32.net \
--cc=kvm-ppc@vger.kernel.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).