From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: kamezawa.hiroyu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com,
davem@davemlloft.net, heiko.carstens@de.ibm.com,
stable@kernel.org
Subject: Re: [PATCH 1/2] clean up for early_pfn_to_nid
Date: Fri, 13 Feb 2009 14:20:32 -0800 [thread overview]
Message-ID: <20090213142032.09b4a4da.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090212162203.db3f07cb.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 12 Feb 2009 16:22:03 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Declaration of early_pfn_to_nid() is scattered over per-arch include files,
> and it seems it's complicated to know when the declaration is used.
> I think it makes fix-for-memmap-init not easy.
>
> This patch moves all declaration to include/linux/mm.h
>
> After this,
> if !CONFIG_NODES_POPULATES_NODE_MAP && !CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID
> -> Use static definition in include/linux/mm.h
> else if !CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID
> -> Use generic definition in mm/page_alloc.c
> else
> -> per-arch back end function will be called.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> ---
> arch/ia64/include/asm/mmzone.h | 4 ----
> arch/ia64/mm/numa.c | 2 +-
> arch/x86/include/asm/mmzone_32.h | 2 --
> arch/x86/include/asm/mmzone_64.h | 2 --
> arch/x86/mm/numa_64.c | 2 +-
> include/linux/mm.h | 19 ++++++++++++++++---
> mm/page_alloc.c | 8 +++++++-
> 7 files changed, 25 insertions(+), 14 deletions(-)
It's rather unfortunate that this bugfix includes a fair-sized cleanup
patch, because we should backport it into 2.6.28.x.
Oh well.
I queued these as
mm-clean-up-for-early_pfn_to_nid.patch
mm-fix-memmap-init-for-handling-memory-hole.patch
and tagged them as needed-in-2.6.28.x. I don't recall whether they are
needed in earlier -stable releases?
I don't have a record here of davem having tested these new patches, btw ;)
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kosaki.motohiro@jp.fujitsu.com, davem@davemlloft.net,
heiko.carstens@de.ibm.com, stable@kernel.org
Subject: Re: [PATCH 1/2] clean up for early_pfn_to_nid
Date: Fri, 13 Feb 2009 14:20:32 -0800 [thread overview]
Message-ID: <20090213142032.09b4a4da.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090212162203.db3f07cb.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 12 Feb 2009 16:22:03 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Declaration of early_pfn_to_nid() is scattered over per-arch include files,
> and it seems it's complicated to know when the declaration is used.
> I think it makes fix-for-memmap-init not easy.
>
> This patch moves all declaration to include/linux/mm.h
>
> After this,
> if !CONFIG_NODES_POPULATES_NODE_MAP && !CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID
> -> Use static definition in include/linux/mm.h
> else if !CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID
> -> Use generic definition in mm/page_alloc.c
> else
> -> per-arch back end function will be called.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> ---
> arch/ia64/include/asm/mmzone.h | 4 ----
> arch/ia64/mm/numa.c | 2 +-
> arch/x86/include/asm/mmzone_32.h | 2 --
> arch/x86/include/asm/mmzone_64.h | 2 --
> arch/x86/mm/numa_64.c | 2 +-
> include/linux/mm.h | 19 ++++++++++++++++---
> mm/page_alloc.c | 8 +++++++-
> 7 files changed, 25 insertions(+), 14 deletions(-)
It's rather unfortunate that this bugfix includes a fair-sized cleanup
patch, because we should backport it into 2.6.28.x.
Oh well.
I queued these as
mm-clean-up-for-early_pfn_to_nid.patch
mm-fix-memmap-init-for-handling-memory-hole.patch
and tagged them as needed-in-2.6.28.x. I don't recall whether they are
needed in earlier -stable releases?
I don't have a record here of davem having tested these new patches, btw ;)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-13 22:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 7:19 [PATCH 0/2] fix memmap init for handling memory hole v2 KAMEZAWA Hiroyuki
2009-02-12 7:19 ` KAMEZAWA Hiroyuki
2009-02-12 7:22 ` [PATCH 1/2] clean up for early_pfn_to_nid KAMEZAWA Hiroyuki
2009-02-12 7:22 ` KAMEZAWA Hiroyuki
2009-02-13 6:14 ` KOSAKI Motohiro
2009-02-13 6:14 ` KOSAKI Motohiro
2009-02-13 22:20 ` Andrew Morton [this message]
2009-02-13 22:20 ` Andrew Morton
2009-02-13 23:38 ` KAMEZAWA Hiroyuki
2009-02-13 23:38 ` KAMEZAWA Hiroyuki
2009-02-14 6:12 ` David Miller
2009-02-14 6:12 ` David Miller
2009-02-16 0:50 ` KAMEZAWA Hiroyuki
2009-02-16 0:50 ` KAMEZAWA Hiroyuki
2009-02-27 6:37 ` David Miller
2009-02-27 6:37 ` David Miller
2009-02-12 7:24 ` [PATCH 2/2] fix memmap init for handling memory hole KAMEZAWA Hiroyuki
2009-02-12 7:24 ` KAMEZAWA Hiroyuki
2009-02-13 6:15 ` KOSAKI Motohiro
2009-02-13 6:15 ` KOSAKI Motohiro
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=20090213142032.09b4a4da.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemlloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@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.