All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: groug@kaod.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org
Cc: lvivier@redhat.com, Thomas Huth <thuth@redhat.com>,
	Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	aik@ozlabs.ru, farosas@linux.ibm.com,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Igor Mammedov <imammedo@redhat.com>,
	paulus@samba.org, Paolo Bonzini <pbonzini@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v6 16/18] spapr: Don't clamp RMA to 16GiB on new machine types
Date: Tue, 25 Feb 2020 10:37:22 +1100	[thread overview]
Message-ID: <20200224233724.46415-17-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20200224233724.46415-1-david@gibson.dropbear.id.au>

In spapr_machine_init() we clamp the size of the RMA to 16GiB and the
comment saying why doesn't make a whole lot of sense.  In fact, this was
done because the real mode handling code elsewhere limited the RMA in TCG
mode to the maximum value configurable in LPCR[RMLS], 16GiB.

But,
 * Actually LPCR[RMLS] has been able to encode a 256GiB size for a very
   long time, we just didn't implement it properly in the softmmu
 * LPCR[RMLS] shouldn't really be relevant anyway, it only was because we
   used to abuse the RMOR based translation mode in order to handle the
   fact that we're not modelling the hypervisor parts of the cpu

We've now removed those limitations in the modelling so the 16GiB clamp no
longer serves a function.  However, we can't just remove the limit
universally: that would break migration to earlier qemu versions, where
the 16GiB RMLS limit still applies, no matter how bad the reasons for it
are.

So, we replace the 16GiB clamp, with a clamp to a limit defined in the
machine type class.  We set it to 16 GiB for machine types 4.2 and earlier,
but set it to 0 meaning unlimited for the new 5.0 machine type.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 hw/ppc/spapr.c         | 13 ++++++++-----
 include/hw/ppc/spapr.h |  1 +
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
index 4dab489931..6e9f15f64d 100644
--- a/hw/ppc/spapr.c
+++ b/hw/ppc/spapr.c
@@ -2702,12 +2702,14 @@ static void spapr_machine_init(MachineState *machine)
 
     spapr->rma_size = node0_size;
 
-    /* Actually we don't support unbounded RMA anymore since we added
-     * proper emulation of HV mode. The max we can get is 16G which
-     * also happens to be what we configure for PAPR mode so make sure
-     * we don't do anything bigger than that
+    /*
+     * Clamp the RMA size based on machine type.  This is for
+     * migration compatibility with older qemu versions, which limited
+     * the RMA size for complicated and mostly bad reasons.
      */
-    spapr->rma_size = MIN(spapr->rma_size, 0x400000000ull);
+    if (smc->rma_limit) {
+        spapr->rma_size = MIN(spapr->rma_size, smc->rma_limit);
+    }
 
     if (spapr->rma_size > node0_size) {
         error_report("Numa node 0 has to span the RMA (%#08"HWADDR_PRIx")",
@@ -4600,6 +4602,7 @@ static void spapr_machine_4_2_class_options(MachineClass *mc)
     compat_props_add(mc->compat_props, hw_compat_4_2, hw_compat_4_2_len);
     smc->default_caps.caps[SPAPR_CAP_CCF_ASSIST] = SPAPR_CAP_OFF;
     smc->default_caps.caps[SPAPR_CAP_FWNMI_MCE] = SPAPR_CAP_OFF;
+    smc->rma_limit = 16 * GiB;
     mc->nvdimm_supported = false;
 }
 
diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
index fc49c1a710..8a44a1f488 100644
--- a/include/hw/ppc/spapr.h
+++ b/include/hw/ppc/spapr.h
@@ -126,6 +126,7 @@ struct SpaprMachineClass {
     bool pre_4_1_migration; /* don't migrate hpt-max-page-size */
     bool linux_pci_probe;
     bool smp_threads_vsmt; /* set VSMT to smp_threads by default */
+    hwaddr rma_limit;          /* clamp the RMA to this size */
 
     void (*phb_placement)(SpaprMachineState *spapr, uint32_t index,
                           uint64_t *buid, hwaddr *pio, 
-- 
2.24.1



  parent reply	other threads:[~2020-02-24 23:50 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 23:37 [PATCH v6 00/18] target/ppc: Correct some errors with real mode handling David Gibson
2020-02-24 23:37 ` [PATCH v6 01/18] pseries: Update SLOF firmware image David Gibson
2020-02-24 23:37 ` [PATCH v6 02/18] ppc: Remove stub support for 32-bit hypervisor mode David Gibson
2020-02-25  6:31   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 03/18] ppc: Remove stub of PPC970 HID4 implementation David Gibson
2020-02-24 23:37 ` [PATCH v6 04/18] target/ppc: Correct handling of real mode accesses with vhyp on hash MMU David Gibson
2020-02-25 10:29   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 05/18] target/ppc: Introduce ppc_hash64_use_vrma() helper David Gibson
2020-02-25  0:12   ` Fabiano Rosas
2020-02-25 10:30   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 06/18] spapr, ppc: Remove VPM0/RMLS hacks for POWER9 David Gibson
2020-02-25 11:29   ` Greg Kurz
2020-02-25 15:58     ` Greg Kurz
2020-02-26  1:00       ` David Gibson
2020-02-24 23:37 ` [PATCH v6 07/18] target/ppc: Remove RMOR register from POWER9 & POWER10 David Gibson
2020-02-25 11:30   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 08/18] target/ppc: Use class fields to simplify LPCR masking David Gibson
2020-02-25 15:48   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 09/18] target/ppc: Streamline calculation of RMA limit from LPCR[RMLS] David Gibson
2020-02-25 17:05   ` Greg Kurz
2020-02-25 22:47     ` Greg Kurz
2020-02-26  1:04       ` David Gibson
2020-02-26  7:56         ` Greg Kurz
2020-02-27  4:25           ` David Gibson
2020-02-24 23:37 ` [PATCH v6 10/18] target/ppc: Correct RMLS table David Gibson
2020-02-26  8:23   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 11/18] target/ppc: Only calculate RMLS derived RMA limit on demand David Gibson
2020-02-26 13:24   ` Greg Kurz
2020-02-27  4:33     ` David Gibson
2020-02-24 23:37 ` [PATCH v6 12/18] target/ppc: Don't store VRMA SLBE persistently David Gibson
2020-02-25  0:25   ` Fabiano Rosas
2020-02-26 13:29   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 13/18] spapr: Don't use weird units for MIN_RMA_SLOF David Gibson
2020-02-25  7:49   ` Cédric Le Goater
2020-02-26 13:32   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 14/18] spapr,ppc: Simplify signature of kvmppc_rma_size() David Gibson
2020-02-24 23:37 ` [PATCH v6 15/18] spapr: Don't attempt to clamp RMA to VRMA constraint David Gibson
2020-02-24 23:37 ` David Gibson [this message]
2020-02-24 23:37 ` [PATCH v6 17/18] spapr: Clean up RMA size calculation David Gibson
2020-02-25 11:07   ` Philippe Mathieu-Daudé
2020-02-26  1:08     ` David Gibson
2020-02-26 13:37   ` Greg Kurz
2020-02-27  6:04     ` David Gibson
2020-02-24 23:37 ` [PATCH v6 18/18] spapr: Fold spapr_node0_size() into its only caller David Gibson
2020-02-26 14:47   ` Greg Kurz

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=20200224233724.46415-17-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=aik@ozlabs.ru \
    --cc=clg@kaod.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=farosas@linux.ibm.com \
    --cc=groug@kaod.org \
    --cc=imammedo@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mst@redhat.com \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=xiaoguangrong.eric@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.