| commit | e6b4e5f4795b2591fd91bea671e3e22e08fd0e75 | |
| author | Alexander Graf <agraf@suse.de> | |
| Fri, 7 Nov 2014 16:07:03 +0000 (7 17:07 +0100) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Wed, 7 Jan 2015 15:16:24 +0000 (7 16:16 +0100) | ||
| tree | 41f303e3b7db2ebfc1a66a8cc6f824d91fc046b1 | treesnapshot (tar.gz zip) |
| parent | 2eaaac1f01014bc7a3597847646a814539494fca | commitdiff |
PPC: e500: Move CCSR and MMIO space to upper end of address space
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 48G.
Signed-off-by: Alexander Graf <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 48G.
Signed-off-by: Alexander Graf <agraf@suse.de>
| hw/ppc/e500plat.c | diffblobblamehistory |