From: KONRAD Frederic <frederic.konrad@adacore.com>
To: david@gibson.dropbear.id.au, agraf@suse.de
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, frederic.konrad@adacore.com
Subject: [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500
Date: Mon, 7 Aug 2017 17:50:44 +0200 [thread overview]
Message-ID: <1502121048-1816-1-git-send-email-frederic.konrad@adacore.com> (raw)
Hi,
Those are some patches to add basic e6500 support for the moment e5500 with a
correct MMU configuration and supported instructions.
Some (maybe a lot of) things are missing (ie: the thread support) but it is
enough to boot a propietary OS on my side.
The first two patches are fixes when using MAV 2.0 MMU.
The two last patches introduces the e6500.
This can be cloned here:
https://github.com/FredKonrad/qemu.git branch e6500
Thanks,
Fred
KONRAD Frederic (4):
booke206: fix booke206_tlbnps for mav 2.0
booke206: fix tlbnps for fixed size TLB
booke206: allow to specify an mmucfg value at the init
ppc64: introduce e6500
target/ppc/cpu-models.c | 2 +
target/ppc/cpu-models.h | 1 +
target/ppc/cpu.h | 26 +++++++++++-
target/ppc/mmu_helper.c | 16 ++++---
target/ppc/translate_init.c | 100 +++++++++++++++++++++++++++++++++++++++++---
5 files changed, 132 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-08-07 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 15:50 KONRAD Frederic [this message]
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 1/4] booke206: fix booke206_tlbnps for mav 2.0 KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 2/4] booke206: fix tlbnps for fixed size TLB KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 3/4] booke206: allow to specify an mmucfg value at the init KONRAD Frederic
2017-08-07 15:50 ` [Qemu-devel] [PATCH for-2.11 4/4] ppc64: introduce e6500 KONRAD Frederic
2017-08-09 7:13 ` [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500 David Gibson
2017-08-11 9:14 ` Alexander Graf
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=1502121048-1816-1-git-send-email-frederic.konrad@adacore.com \
--to=frederic.konrad@adacore.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).