[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110713091613.GE2872@htj.dyndns.org>
Date: Wed, 13 Jul 2011 11:16:13 +0200
From: Tejun Heo <tj@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Yinghai Lu <yinghai@...nel.org>, mingo@...hat.com,
tglx@...utronix.de, benh@...nel.crashing.org, davem@...emloft.net,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
x86@...nel.org
Subject: Re: [PATCHSET x86/mm] memblock, x86: Allow node info in memblock and
remove x86 specific memblock code
Hello,
On Tue, Jul 12, 2011 at 08:21:23PM -0700, H. Peter Anvin wrote:
> On 07/12/2011 04:26 PM, Yinghai Lu wrote:
> >
> > that is great, merge early_node_map into memblock array.
> >
> > looks it comes with some mismatch section warning...
> >
>
> I'm also confused about the baseline of the patchset...
The whole thing is on top of x86/urgent for the commit which disabled
AMD NUMA on 32bit, so it's like the following.
x86/urgent (5da0ef9a8 "x86: Disable AMD_NUMA for 32bit for now")
+ Two patches for pfn->nid mapping granularity check (applied now)
http://thread.gmane.org/gmane.linux.kernel/1166521
+ memblock, x86: Misc cleanups
http://thread.gmane.org/gmane.linux.kernel.cross-arch/10338
+ memblock, x86: Implement for_each_mem_pfn_range() and use it to improve memblock allocator
http://thread.gmane.org/gmane.linux.kernel.cross-arch/10345
+ memblock, x86: Allow node info in memblock and remove x86 specific memblock code
http://thread.gmane.org/gmane.linux.kernel.cross-arch/10354
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists