qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, imammedo@redhat.com,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	ehabkost@redhat.com, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [RFC PATCH v1 3/4] numa: Store boot memory address range in node_info
Date: Fri, 12 Jun 2015 14:30:27 +0530	[thread overview]
Message-ID: <1434099628-18102-4-git-send-email-bharata@linux.vnet.ibm.com> (raw)
In-Reply-To: <1434099628-18102-1-git-send-email-bharata@linux.vnet.ibm.com>

Store memory address range information of boot memory  in address
range list of numa_info.

This helps to have a common NUMA node lookup by address function that
works for both boot time memory and hotplugged memory.

Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
---
 numa.c | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/numa.c b/numa.c
index 27ca743..d67b1fb 100644
--- a/numa.c
+++ b/numa.c
@@ -75,6 +75,26 @@ void numa_unset_mem_node_id(ram_addr_t addr, uint64_t size, uint32_t node)
     }
 }
 
+static void numa_set_mem_ranges(void)
+{
+    int i;
+    ram_addr_t mem_start, mem_end_prev;
+
+    /*
+     * Deduce start address of each node and use it to store
+     * the address range info in numa_info address range list
+     */
+    for (i = 0; i < nb_numa_nodes; i++) {
+        if (i) {
+            mem_start = mem_end_prev;
+        } else {
+            mem_start = 0;
+        }
+        mem_end_prev = mem_start + numa_info[i].node_mem;
+        numa_set_mem_node_id(mem_start, numa_info[i].node_mem, i);
+    }
+}
+
 static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp)
 {
     uint16_t nodenr;
@@ -300,6 +320,8 @@ void parse_numa_opts(MachineClass *mc)
             QLIST_INIT(&numa_info[i].addr);
         }
 
+        numa_set_mem_ranges();
+
         for (i = 0; i < nb_numa_nodes; i++) {
             if (!bitmap_empty(numa_info[i].node_cpu, MAX_CPUMASK_BITS)) {
                 break;
-- 
2.1.0

  parent reply	other threads:[~2015-06-12  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  9:00 [Qemu-devel] [RFC PATCH v1 0/4] Refactoring pc_dimm_plug and NUMA node lookup API Bharata B Rao
2015-06-12  9:00 ` [Qemu-devel] [RFC PATCH v1 1/4] pc, pc-dimm: Factor out reusable parts in pc_dimm_plug to a separate routine Bharata B Rao
2015-06-15  6:32   ` David Gibson
2015-06-12  9:00 ` [Qemu-devel] [RFC PATCH v1 2/4] numa, pc-dimm: Store pc-dimm memory information in numa_info Bharata B Rao
2015-06-15  6:34   ` David Gibson
2015-06-15  9:17   ` Igor Mammedov
2015-06-15 13:04     ` Bharata B Rao
2015-06-12  9:00 ` Bharata B Rao [this message]
2015-06-15  6:35   ` [Qemu-devel] [RFC PATCH v1 3/4] numa: Store boot memory address range in node_info David Gibson
2015-06-15 16:31   ` Eduardo Habkost
2015-06-17  3:17     ` Bharata B Rao
2015-06-12  9:00 ` [Qemu-devel] [RFC PATCH v1 4/4] numa: API to lookup NUMA node by address Bharata B Rao
2015-06-15  6:35   ` David Gibson

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=1434099628-18102-4-git-send-email-bharata@linux.vnet.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).