qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: bharata@linux.vnet.ibm.com
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 5/6] numa: Store boot memory address range in node_info
Date: Thu, 9 Jul 2015 17:18:48 +0200	[thread overview]
Message-ID: <559E90D8.8080706@redhat.com> (raw)
In-Reply-To: <20150709151004.GA4827@in.ibm.com>



On 09/07/2015 17:10, Bharata B Rao wrote:
> On Thu, Jul 09, 2015 at 04:12:09PM +0200, Paolo Bonzini wrote:
>>
>>
>> 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".
> 
> Should I post this fix as an independent thread ?

Yes, please.

Paolo

> 
> numa: Fix memory leak in numa_set_mem_node_id()
> 
> From: Bharata B Rao <bharata@linux.vnet.ibm.com>
> 
> Fix a memory leak in numa_set_mem_node_id().
> 
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.com>
> ---
>  numa.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/numa.c b/numa.c
> index 3c80059..402804b 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -54,7 +54,7 @@ NodeInfo numa_info[MAX_NODES];
>  
>  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));
> +    struct numa_addr_range *range;
>  
>      /*
>       * Memory-less nodes can come here with 0 size in which case,
> @@ -64,6 +64,7 @@ void numa_set_mem_node_id(ram_addr_t addr, uint64_t size, uint32_t node)
>          return;
>      }
>  
> +    range = g_malloc0(sizeof(*range));
>      range->mem_start = addr;
>      range->mem_end = addr + size - 1;
>      QLIST_INSERT_HEAD(&numa_info[node].addr, range, entry);
> 

  reply	other threads:[~2015-07-09 15:18 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
2015-07-09 15:10     ` Bharata B Rao
2015-07-09 15:18       ` Paolo Bonzini [this message]
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=559E90D8.8080706@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).