From: Yinghai Lu <yinghai@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, mm: clean up setup_node_bootmem
Date: Thu, 03 Mar 2011 13:35:54 -0800 [thread overview]
Message-ID: <4D7009BA.5030600@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103031243020.9993@chino.kir.corp.google.com>
On 03/03/2011 12:49 PM, David Rientjes wrote:
> On Wed, 2 Mar 2011, Yinghai Lu wrote:
>
>>
>> only one user now, so change it to static
>>
>> Also move validity checking into the fuction.
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>> ---
>> arch/x86/include/asm/numa_64.h | 2 --
>> arch/x86/mm/numa_64.c | 10 +++-------
>> 2 files changed, 3 insertions(+), 9 deletions(-)
>>
>> Index: linux-2.6/arch/x86/include/asm/numa_64.h
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/include/asm/numa_64.h
>> +++ linux-2.6/arch/x86/include/asm/numa_64.h
>> @@ -13,8 +13,6 @@ struct bootnode {
>> extern int numa_off;
>>
>> extern unsigned long numa_free_all_bootmem(void);
>> -extern void setup_node_bootmem(int nodeid, unsigned long start,
>> - unsigned long end);
>>
>> #ifdef CONFIG_NUMA
>> /*
>> Index: linux-2.6/arch/x86/mm/numa_64.c
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/mm/numa_64.c
>> +++ linux-2.6/arch/x86/mm/numa_64.c
>> @@ -237,21 +237,18 @@ int __init numa_add_memblk(int nid, u64
>> }
>>
>> /* Initialize bootmem allocator for a node */
>> -void __init
>> +static void __init
>> setup_node_bootmem(int nodeid, unsigned long start, unsigned long end)
>> {
>> unsigned long start_pfn, last_pfn, nodedata_phys;
>> const int pgdat_size = roundup(sizeof(pg_data_t), PAGE_SIZE);
>> int nid;
>>
>> - if (!end)
>> - return;
>> -
>> /*
>> * Don't confuse VM with a node that doesn't have the
>> * minimum amount of memory:
>> */
>> - if (end && (end - start) < NODE_MIN_SIZE)
>> + if (end < (start + NODE_MIN_SIZE))
>> return;
>>
>> start = roundup(start, ZONE_ALIGN);
>> @@ -557,8 +554,7 @@ static int __init numa_register_memblks(
>> end = max(mi->blk[i].end, end);
>> }
>>
>> - if (start < end)
>> - setup_node_bootmem(nid, start, end);
>> + setup_node_bootmem(nid, start, end);
>> }
>>
>> return 0;
>>
>
> Good catch on finding only the one caller of setup_node_bootmem().
>
> I'd actually rather see the validity checking being done in
> numa_register_memblks(), though, because it's a bug for a node to be set
> in node_possible_map without having a valid
> [mi->blk[i].start, mi->blk[i].end) range.
>
> So could this be
>
> BUG_ON(end < start);
no, it could cause crash here
/* Finally register nodes. */
for_each_node_mask(nid, node_possible_map) {
u64 start = (u64)max_pfn << PAGE_SHIFT;
u64 end = 0;
for (i = 0; i < mi->nr_blks; i++) {
if (nid != mi->blk[i].nid)
continue;
start = min(mi->blk[i].start, start);
end = max(mi->blk[i].end, end);
}
could have some node without memory. and it could be set in node_possible_map, and it will have end = 0, and start max_pfn<<page_shift.
> /*
> * Don't confuse the VM with a node that doesn't have the minimum
> * amount of memory.
> */
> if (end < start + NODE_MIN_SIZE) {
> node_clear(nid, node_possible_map);
why touch that possible_map ?
online_map is for that purpose that state node have ram.
> continue;
> }
> setup_node_bootmem(nid, start, end);
>
> instead?
Thanks
Yinghai
next prev parent reply other threads:[~2011-03-03 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 1:19 [PATCH] x86, mm: clean up setup_node_bootmem Yinghai Lu
2011-03-03 6:30 ` Tejun Heo
2011-03-03 20:49 ` David Rientjes
2011-03-03 21:35 ` Yinghai Lu [this message]
2011-03-03 22:04 ` David Rientjes
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=4D7009BA.5030600@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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 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.