qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Nishanth Aravamudan <nacc@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v3 4/6] spapr: Split memory nodes to power-of-two blocks
Date: Thu,  3 Jul 2014 13:10:05 +1000	[thread overview]
Message-ID: <1404357007-29507-5-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1404357007-29507-1-git-send-email-aik@ozlabs.ru>

Linux kernel expects nodes to have power-of-two size and
does WARN_ON if this is not the case:
[    0.041456] WARNING: at drivers/base/memory.c:115
which is:
===
	/* Validate blk_sz is a power of 2 and not less than section size */
	if ((block_sz & (block_sz - 1)) || (block_sz < MIN_MEMORY_BLOCK_SIZE)) {
        	WARN_ON(1);
	        block_sz = MIN_MEMORY_BLOCK_SIZE;
	}
===

This splits memory nodes into set of smaller blocks with
a size which is a power of two. This makes sure the start
address of every node is aligned to the node size.

Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
Changes:
v3:
* s/ffs/ffsl/ as addresses are 64bit long

v2:
* tiny code cleanup in "sizetmp = MIN(sizetmp, 1 << (ffs(mem_start) - 1))"
* updated commit log with a piece of kernel code doing WARN_ON
---
 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 ec6d541..680d7f9 100644
--- a/hw/ppc/spapr.c
+++ b/hw/ppc/spapr.c
@@ -662,8 +662,18 @@ static int spapr_populate_memory(sPAPREnvironment *spapr, void *fdt)
             mem_start += spapr->rma_size;
             node_size -= spapr->rma_size;
         }
-        spapr_populate_memory_node(fdt, i, mem_start, node_size);
-        mem_start += node_size;
+        for ( ; node_size; ) {
+            hwaddr sizetmp = pow2floor(node_size);
+
+            /* mem_start != 0 here */
+            if (ffsl(mem_start) < ffsl(sizetmp)) {
+                sizetmp = 1ULL << (ffsl(mem_start) - 1);
+            }
+
+            spapr_populate_memory_node(fdt, i, mem_start, sizetmp);
+            node_size -= sizetmp;
+            mem_start += sizetmp;
+        }
     }
 
     return 0;
-- 
2.0.0

  parent reply	other threads:[~2014-07-03  3:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  3:10 [Qemu-devel] [PATCH v3 0/6] spapr: rework memory nodes Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 1/6] spapr: Move DT memory node rendering to a helper Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 2/6] spapr: Use DT memory node rendering helper for other nodes Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 3/6] spapr: Refactor spapr_populate_memory() to allow memoryless nodes Alexey Kardashevskiy
2014-07-03  3:10 ` Alexey Kardashevskiy [this message]
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 5/6] spapr: Add a helper for node0_size calculation Alexey Kardashevskiy
2014-07-03  3:10 ` [Qemu-devel] [PATCH v3 6/6] spapr: Fix ibm, associativity for memory nodes Alexey Kardashevskiy
2014-07-21  3:15 ` [Qemu-devel] [PATCH v3 0/6] spapr: rework " Alexey Kardashevskiy
2014-07-28 11:02   ` Alexander Graf

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=1404357007-29507-5-git-send-email-aik@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=nacc@linux.vnet.ibm.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).