All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: qemu-ppc@nongnu.org, groug@kaod.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, Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, 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 v5 18/18] spapr: Fold spapr_node0_size() into its only caller
Date: Thu, 20 Feb 2020 14:23:16 +1100	[thread overview]
Message-ID: <20200220032317.96884-19-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20200220032317.96884-1-david@gibson.dropbear.id.au>

The Real Mode Area (RMA) needs to fit within the NUMA node owning memory
at address 0.  That's usually node 0, but can be a later one if there are
some nodes which have no memory (only CPUs).

This is currently handled by the spapr_node0_size() helper.  It has only
one caller, so there's not a lot of point splitting it out.  It's also
extremely easy to misread the code as clamping to the size of the smallest
node rather than the first node with any memory.

So, fold it into the caller, and add some commentary to make it a bit
clearer exactly what it's doing.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 hw/ppc/spapr.c | 37 +++++++++++++++++++++----------------
 1 file changed, 21 insertions(+), 16 deletions(-)

diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
index f0354b699d..9ba645c9cb 100644
--- a/hw/ppc/spapr.c
+++ b/hw/ppc/spapr.c
@@ -296,20 +296,6 @@ static void spapr_populate_pa_features(SpaprMachineState *spapr,
     _FDT((fdt_setprop(fdt, offset, "ibm,pa-features", pa_features, pa_size)));
 }
 
-static hwaddr spapr_node0_size(MachineState *machine)
-{
-    if (machine->numa_state->num_nodes) {
-        int i;
-        for (i = 0; i < machine->numa_state->num_nodes; ++i) {
-            if (machine->numa_state->nodes[i].node_mem) {
-                return MIN(pow2floor(machine->numa_state->nodes[i].node_mem),
-                           machine->ram_size);
-            }
-        }
-    }
-    return machine->ram_size;
-}
-
 static void add_str(GString *s, const gchar *s1)
 {
     g_string_append_len(s, s1, strlen(s1) + 1);
@@ -2652,10 +2638,24 @@ static hwaddr spapr_rma_size(SpaprMachineState *spapr, Error **errp)
 {
     MachineState *machine = MACHINE(spapr);
     hwaddr rma_size = machine->ram_size;
-    hwaddr node0_size = spapr_node0_size(machine);
 
     /* RMA has to fit in the first NUMA node */
-    rma_size = MIN(rma_size, node0_size);
+    if (machine->numa_state->num_nodes) {
+        /*
+         * It's possible for there to be some zero-memory nodes first
+         * in the list.  We need the RMA to fit inside the memory of
+         * the first node which actually has some memory.
+         */
+        int i;
+
+        for (i = 0; i < machine->numa_state->num_nodes; ++i) {
+            if (machine->numa_state->nodes[i].node_mem != 0) {
+                rma_size = MIN(rma_size,
+                               machine->numa_state->nodes[i].node_mem);
+                break;
+            }
+        }
+    }
 
     /*
      * VRMA access is via a special 1TiB SLB mapping, so the RMA can
@@ -2672,6 +2672,11 @@ static hwaddr spapr_rma_size(SpaprMachineState *spapr, Error **errp)
         spapr->rma_size = MIN(spapr->rma_size, smc->rma_limit);
     }
 
+    /*
+     * RMA size must be a power of 2
+     */
+    rma_size = pow2floor(rma_size);
+
     if (rma_size < (MIN_RMA_SLOF * MiB)) {
         error_setg(errp,
 "pSeries SLOF firmware requires >= %ldMiB guest RMA (Real Mode Area)",
-- 
2.24.1



      parent reply	other threads:[~2020-02-20  3:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  3:22 [PATCH v5 00/18] target/ppc: Correct some errors with real mode handling David Gibson
2020-02-20  3:22 ` [PATCH v5 01/18] ppc: Remove stub support for 32-bit hypervisor mode David Gibson
2020-02-20  3:23 ` [PATCH v5 02/18] ppc: Remove stub of PPC970 HID4 implementation David Gibson
2020-02-20  3:23 ` [PATCH v5 03/18] target/ppc: Correct handling of real mode accesses with vhyp on hash MMU David Gibson
2020-02-20  3:23 ` [PATCH v5 04/18] target/ppc: Introduce ppc_hash64_use_vrma() helper David Gibson
2020-02-20  3:23 ` [PATCH v5 05/18] spapr, ppc: Remove VPM0/RMLS hacks for POWER9 David Gibson
2020-02-20  3:23 ` [PATCH v5 06/18] target/ppc: Remove RMOR register from POWER9 & POWER10 David Gibson
2020-02-20  3:23 ` [PATCH v5 07/18] target/ppc: Use class fields to simplify LPCR masking David Gibson
2020-02-20  3:23 ` [PATCH v5 08/18] target/ppc: Streamline calculation of RMA limit from LPCR[RMLS] David Gibson
2020-02-20  3:23 ` [PATCH v5 09/18] target/ppc: Correct RMLS table David Gibson
2020-02-20  3:23 ` [PATCH v5 10/18] target/ppc: Only calculate RMLS derived RMA limit on demand David Gibson
2020-02-20  3:23 ` [PATCH v5 11/18] target/ppc: Streamline construction of VRMA SLB entry David Gibson
2020-02-20  3:23 ` [PATCH v5 12/18] target/ppc: Don't store VRMA SLBE persistently David Gibson
2020-02-20  3:23 ` [PATCH v5 13/18] spapr: Don't use weird units for MIN_RMA_SLOF David Gibson
2020-02-20  3:23 ` [PATCH v5 14/18] spapr,ppc: Simplify signature of kvmppc_rma_size() David Gibson
2020-02-20  3:23 ` [PATCH v5 15/18] spapr: Don't attempt to clamp RMA to VRMA constraint David Gibson
2020-02-20  3:23 ` [PATCH v5 16/18] spapr: Don't clamp RMA to 16GiB on new machine types David Gibson
2020-02-20  3:23 ` [PATCH v5 17/18] spapr: Clean up RMA size calculation David Gibson
2020-02-20  3:23 ` David Gibson [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=20200220032317.96884-19-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=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.