From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL 5/6] numa: Store boot memory address range in node_info
Date: Thu, 9 Jul 2015 16:12:09 +0200 [thread overview]
Message-ID: <559E8139.8030809@redhat.com> (raw)
In-Reply-To: <1435956624-21609-6-git-send-email-ehabkost@redhat.com>
On 03/07/2015 22:50, Eduardo Habkost wrote:
> From: Bharata B Rao <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>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Tested-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> numa.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/numa.c b/numa.c
> index 116d1fb..a73f648 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -56,6 +56,14 @@ void numa_set_mem_node_id(ram_addr_t addr, uint64_t size, uint32_t node)
> {
> struct numa_addr_range *range = g_malloc0(sizeof(*range));
>
> + /*
> + * Memory-less nodes can come here with 0 size in which case,
> + * there is nothing to do.
> + */
> + if (!size) {
> + return;
This leaks "range".
Paolo
> + }
> +
> range->mem_start = addr;
> range->mem_end = addr + size - 1;
> QLIST_INSERT_HEAD(&numa_info[node].addr, range, entry);
> @@ -74,6 +82,21 @@ 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 = 0;
> +
> + /*
> + * 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++) {
> + numa_set_mem_node_id(mem_start, numa_info[i].node_mem, i);
> + mem_start += numa_info[i].node_mem;
> + }
> +}
> +
> static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp)
> {
> uint16_t nodenr;
> @@ -299,6 +322,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;
> @@ -323,6 +348,8 @@ void parse_numa_opts(MachineClass *mc)
> }
>
> validate_numa_cpus();
> + } else {
> + numa_set_mem_node_id(0, ram_size, 0);
> }
> }
>
>
next prev parent reply other threads:[~2015-07-09 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 20:50 [Qemu-devel] [PULL 0/6] NUMA queue, 2015-07-03 Eduardo Habkost
2015-07-03 20:50 ` [Qemu-devel] [PULL 1/6] pc, pc-dimm: Extract hotplug related fields in PCMachineState to a structure Eduardo Habkost
2015-07-03 20:50 ` [Qemu-devel] [PULL 2/6] pc, pc-dimm: Factor out reusable parts in pc_dimm_plug to a separate routine Eduardo Habkost
2015-07-03 20:50 ` [Qemu-devel] [PULL 3/6] pc: Abort if HotplugHandlerClass::plug() fails Eduardo Habkost
2015-07-03 20:50 ` [Qemu-devel] [PULL 4/6] numa, pc-dimm: Store pc-dimm memory information in numa_info Eduardo Habkost
2015-07-03 20:50 ` [Qemu-devel] [PULL 5/6] numa: Store boot memory address range in node_info Eduardo Habkost
2015-07-09 14:12 ` Paolo Bonzini [this message]
2015-07-09 15:10 ` Bharata B Rao
2015-07-09 15:18 ` Paolo Bonzini
2015-07-03 20:50 ` [Qemu-devel] [PULL 6/6] numa: API to lookup NUMA node by address Eduardo Habkost
2015-07-05 19:35 ` [Qemu-devel] [PULL 0/6] NUMA queue, 2015-07-03 Peter Maydell
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=559E8139.8030809@redhat.com \
--to=pbonzini@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).