From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, benh@kernel.crashing.org,
thuth@redhat.com, agraf@suse.de, mst@redhat.com, aik@ozlabs.ru,
mdroth@linux.vnet.ibm.com, nikunj@linux.vnet.ibm.com,
bharata@linux.vnet.ibm.com, abologna@redhat.com,
mpolednik@redhat.com
Subject: Re: [Qemu-devel] [RFC 2/4] spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM
Date: Thu, 6 Oct 2016 11:36:47 +0200 [thread overview]
Message-ID: <52f34db7-0ae1-cca2-3bd2-e67d70ab2f3f@redhat.com> (raw)
In-Reply-To: <1475722987-18644-3-git-send-email-david@gibson.dropbear.id.au>
On 06/10/2016 05:03, David Gibson wrote:
> 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>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/ppc/spapr.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index f6e9c2a..9f3e004 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -2376,12 +2376,15 @@ 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 */
>
> + uint64_t max_hotplug_addr = spapr->hotplug_memory.base +
> + memory_region_size(&spapr->hotplug_memory.mr);
> + hwaddr phb0_base = QEMU_ALIGN_UP(max_hotplug_addr, phb0_alignment);
> hwaddr phb_base;
> int i;
>
>
next prev parent reply other threads:[~2016-10-06 9:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 3:03 [Qemu-devel] [RFC 0/4] Improve PCI IO window orgnaization for pseries David Gibson
2016-10-06 3:03 ` [Qemu-devel] [RFC 1/4] spapr_pci: Delegate placement of PCI host bridges to machine type David Gibson
2016-10-06 7:10 ` Laurent Vivier
2016-10-06 8:11 ` David Gibson
2016-10-06 9:36 ` Laurent Vivier
2016-10-06 23:51 ` David Gibson
2016-10-07 3:57 ` Alexey Kardashevskiy
2016-10-07 5:10 ` David Gibson
2016-10-07 5:34 ` Alexey Kardashevskiy
2016-10-07 9:17 ` David Gibson
2016-10-10 1:04 ` Alexey Kardashevskiy
2016-10-10 4:07 ` David Gibson
2016-10-11 3:17 ` David Gibson
2016-10-06 3:03 ` [Qemu-devel] [RFC 2/4] spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM David Gibson
2016-10-06 7:21 ` Laurent Vivier
2016-10-06 8:46 ` David Gibson
2016-10-06 9:36 ` Laurent Vivier [this message]
2016-10-06 3:03 ` [Qemu-devel] [RFC 3/4] spapr_pci: Add a 64-bit MMIO window David Gibson
2016-10-06 3:03 ` [Qemu-devel] [RFC 4/4] spapr: Improved placement of PCI host bridges in guest memory map David Gibson
2016-10-10 15:53 ` [Qemu-devel] [RFC 0/4] 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=52f34db7-0ae1-cca2-3bd2-e67d70ab2f3f@redhat.com \
--to=lvivier@redhat.com \
--cc=abologna@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mpolednik@redhat.com \
--cc=mst@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).