From: Alexander Graf <agraf@suse.de>
To: qemu-ppc@nongnu.org
Cc: stuart.yoder@freescale.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 0/4] PPC: e500: Support more RAM
Date: Wed, 12 Nov 2014 22:56:36 +0100 [thread overview]
Message-ID: <1415829400-58216-1-git-send-email-agraf@suse.de> (raw)
The e500 target today only supports 3GB of guest RAM. This can be too
little depending on your use case, so this patch set increases that limit
to a whopping 48GB!
Of course this change is too intrusive for 2.2, so I'm posting this
explicitly for 2.3.
v1 -> v2:
- make pci pio window device tree exposure dynamic
v2 -> v3:
- rename pci_base to pci_pio_base
- add ATMU support
Alex
Alexander Graf (4):
PPC: e500: Move CCSR definition to params
PPC: e500: Move CCSR and MMIO space to upper end of address space
PPC: mpc8554ds: Tell user about exceeding RAM limits
PPC: e500 pci host: Add support for ATMUs
hw/pci-host/ppce500.c | 113 +++++++++++++++++++++++++++++++++++++++++++++++---
hw/ppc/e500.c | 34 +++++++--------
hw/ppc/e500.h | 5 +++
hw/ppc/e500plat.c | 5 +++
hw/ppc/mpc8544ds.c | 11 +++++
5 files changed, 143 insertions(+), 25 deletions(-)
--
1.8.1.4
next reply other threads:[~2014-11-12 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 21:56 Alexander Graf [this message]
2014-11-12 21:56 ` [Qemu-devel] [PATCH v3 1/4] PPC: e500: Move CCSR definition to params Alexander Graf
2014-11-12 21:56 ` [Qemu-devel] [PATCH v3 2/4] PPC: e500: Move CCSR and MMIO space to upper end of address space Alexander Graf
2014-11-12 21:56 ` [Qemu-devel] [PATCH v3 3/4] PPC: mpc8554ds: Tell user about exceeding RAM limits Alexander Graf
2014-11-12 21:56 ` [Qemu-devel] [PATCH v3 4/4] PPC: e500 pci host: Add support for ATMUs Alexander Graf
2014-11-13 15:08 ` [Qemu-devel] [Qemu-ppc] " Bharat.Bhushan
2014-11-13 19:06 ` 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=1415829400-58216-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stuart.yoder@freescale.com \
/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).