From: David Gibson <david@gibson.dropbear.id.au>
To: lvivier@redhat.com, agraf@suse.de
Cc: mst@redhat.com, abolonga@redhat.com, aik@ozlabs.ru,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
mdroth@linux.vnet.ibm.com, benh@kernel.crashing.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH 5/7] spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM
Date: Wed, 12 Oct 2016 15:29:50 +1100 [thread overview]
Message-ID: <1476246592-24228-6-git-send-email-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <1476246592-24228-1-git-send-email-david@gibson.dropbear.id.au>
Currently the default PCI host bridge for the 'pseries' machine type is
constructed with its IO windows in the 1TiB..(1TiB + 64GiB) range in
guest memory space. This means that if > 1TiB of guest RAM is specified,
the RAM will collide with the PCI IO windows, causing serious problems.
Problems won't be obvious until guest RAM goes a bit beyond 1TiB, because
there's a little unused space at the bottom of the area reserved for PCI,
but essentially this means that > 1TiB of RAM has never worked with the
pseries machine type.
This patch fixes this by altering the placement of PHBs on large-RAM VMs.
Instead of always placing the first PHB at 1TiB, it is placed at the next
1 TiB boundary after the maximum RAM address.
Technically, this changes behaviour in a migration-breaking way for
existing machines with > 1TiB maximum memory, but since having > 1 TiB
memory was broken anyway, this seems like a reasonable trade-off.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
hw/ppc/spapr.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
index f6e9c2a..08a8327 100644
--- a/hw/ppc/spapr.c
+++ b/hw/ppc/spapr.c
@@ -2376,15 +2376,25 @@ static void spapr_phb_placement(sPAPRMachineState *spapr, uint32_t index,
unsigned n_dma, uint32_t *liobns, Error **errp)
{
const uint64_t base_buid = 0x800000020000000ULL;
- const hwaddr phb0_base = 0x10000000000ULL; /* 1 TiB */
const hwaddr phb_spacing = 0x1000000000ULL; /* 64 GiB */
const hwaddr mmio_offset = 0xa0000000; /* 2 GiB + 512 MiB */
const hwaddr pio_offset = 0x80000000; /* 2 GiB */
const uint32_t max_index = 255;
+ const hwaddr phb0_alignment = 0x10000000000ULL; /* 1 TiB */
- hwaddr phb_base;
+ uint64_t ram_top = MACHINE(spapr)->ram_size;
+ hwaddr phb0_base, phb_base;
int i;
+ if (MACHINE(spapr)->maxram_size > ram_top) {
+ ram_top = spapr->hotplug_memory.base +
+ memory_region_size(&spapr->hotplug_memory.mr);
+ }
+
+ phb0_base = QEMU_ALIGN_UP(ram_top, phb0_alignment);
+
+ fprintf(stderr, "DEBUG: ram_top = 0x%016"PRIx64" phb0 @ 0x%016"HWADDR_PRIX"\n",
+ ram_top, phb0_base);
if (index > max_index) {
error_setg(errp, "\"index\" for PAPR PHB is too large (max %u)",
max_index);
--
2.7.4
next prev parent reply other threads:[~2016-10-12 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 4:29 [Qemu-devel] [PATCH 0/7] Improve PCI IO window orgnaization for pseries David Gibson
2016-10-12 4:29 ` [Qemu-devel] [PATCH 1/7] libqos: Isolate knowledge of spapr memory map to qpci_init_spapr() David Gibson
2016-10-12 4:29 ` [Qemu-devel] [PATCH 2/7] libqos: Correct error in PCI hole sizing for spapr David Gibson
2016-10-12 4:29 ` [Qemu-devel] [PATCH 3/7] libqos: Limit spapr-pci to 32-bit MMIO for now David Gibson
2016-10-12 4:29 ` [Qemu-devel] [PATCH 4/7] spapr_pci: Delegate placement of PCI host bridges to machine type David Gibson
2016-10-12 4:29 ` David Gibson [this message]
2016-10-12 4:29 ` [Qemu-devel] [PATCH 6/7] spapr_pci: Add a 64-bit MMIO window David Gibson
2016-10-12 4:29 ` [Qemu-devel] [PATCH 7/7] spapr: Improved placement of PCI host bridges in guest memory map David Gibson
2016-10-12 4:43 ` [Qemu-devel] [PATCH 0/7] IGNORE, SORRY (was: Improve PCI IO window orgnaization for pseries) David Gibson
2016-10-12 8:26 ` [Qemu-devel] [PATCH 0/7] Improve PCI IO window orgnaization for pseries no-reply
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=1476246592-24228-6-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=abolonga@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--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).