From: Alexander Graf <agraf@suse.de>
To: qemu-ppc@nongnu.org
Cc: stuart.yoder@freescale.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 2/2] PPC: e500: Move CCSR and MMIO space to upper end of address space
Date: Sat, 8 Nov 2014 00:34:21 +0100 [thread overview]
Message-ID: <1415403261-27089-3-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1415403261-27089-1-git-send-email-agraf@suse.de>
On e500 we're basically guaranteed to have 36bits of physical address space
available for our enjoyment. Older chips (like the mpc8544) only had 32bits,
but everything from e500v2 onwards bumped it up.
It's reasonably safe to assume that if you're using the PV machine, your guest
kernel is configured to support 36bit physical address space. So in order to
support more guest RAM, we can move CCSR and other MMIO windows right below the
end of our 36bit address space, just like later SoC versions of e500 do.
With this patch, I'm able to successfully spawn an e500 VM with -m 60G.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
hw/ppc/e500plat.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/ppc/e500plat.c b/hw/ppc/e500plat.c
index 213a2f8..3540822 100644
--- a/hw/ppc/e500plat.c
+++ b/hw/ppc/e500plat.c
@@ -41,9 +41,9 @@ static void e500plat_init(MachineState *machine)
.platform_bus_size = (128ULL * 1024 * 1024),
.platform_bus_first_irq = 5,
.platform_bus_num_irqs = 10,
- .ccsrbar_base = 0xE0000000ULL,
- .pci_base = 0xE1000000ULL,
- .spin_base = 0xEF000000ULL,
+ .ccsrbar_base = 0xFE0000000ULL,
+ .pci_base = 0xFE1000000ULL,
+ .spin_base = 0xFEF000000ULL,
};
/* Older KVM versions don't support EPR which breaks guests when we announce
--
1.8.1.4
prev parent reply other threads:[~2014-11-07 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 23:34 [Qemu-devel] [PATCH v2 0/2] PPC: e500: Support more RAM Alexander Graf
2014-11-07 23:34 ` [Qemu-devel] [PATCH v2 1/2] PPC: e500: Move CCSR definition to params Alexander Graf
2014-11-07 23:34 ` Alexander Graf [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=1415403261-27089-3-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).