From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
davem@davemlloft.net, heiko.carstens@de.ibm.com,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 2/2] fix memmap init for handling memory hole
Date: Fri, 13 Feb 2009 15:15:14 +0900 (JST) [thread overview]
Message-ID: <20090213151455.77CE.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090212162421.65bb7aa2.kamezawa.hiroyu@jp.fujitsu.com>
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> Now, early_pfn_in_nid(PFN, NID) may returns false if PFN is a hole.
> and memmap initialization was not done. This was a trouble for
> sparc boot.
>
> To fix this, the PFN should be initialized and marked as PG_reserved.
> This patch changes early_pfn_in_nid() return true if PFN is a hole.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
at least, this patch works fine on my ia64 box.
Tested-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
--
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>
prev parent reply other threads:[~2009-02-13 6:15 UTC|newest]
Thread overview: 10+ 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:22 ` [PATCH 1/2] clean up for early_pfn_to_nid KAMEZAWA Hiroyuki
2009-02-13 6:14 ` KOSAKI Motohiro
2009-02-13 22:20 ` Andrew Morton
2009-02-13 23:38 ` KAMEZAWA Hiroyuki
2009-02-14 6:12 ` David Miller
2009-02-16 0:50 ` KAMEZAWA Hiroyuki
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-13 6:15 ` KOSAKI Motohiro [this message]
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=20090213151455.77CE.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemlloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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