From: Mel Gorman <mel@csn.ul.ie>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Shi Weihua <shiwh@cn.fujitsu.com>,
akpm@linux-foundation.org, balbir@linux.vnet.ibm.com,
xemul@openvz.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, hugh@veritas.com
Subject: Re: [PATCH]Fix usemap for DISCONTIG/FLATMEM with not-aligned zone initilaization.
Date: Mon, 21 Apr 2008 11:12:32 +0100 [thread overview]
Message-ID: <20080421101231.GA629@csn.ul.ie> (raw)
In-Reply-To: <20080421112048.78f0ec76.kamezawa.hiroyu@jp.fujitsu.com>
On (21/04/08 11:20), KAMEZAWA Hiroyuki didst pronounce:
> On Sat, 19 Apr 2008 02:25:56 +0900 (JST)
> kamezawa.hiroyu@jp.fujitsu.com wrote:
>
> > >What about something like the following? Instead of expanding the size of
> > >structures, it sanity checks input parameters. It touches a number of places
> > >because of an API change but it is otherwise straight-forward.
> > >
> > >Unfortunately, I do not have an IA-64 machine that can reproduce the problem
> > >to see if this still fixes it or not so a test as well as a review would be
> > >appreciated. What should happen is the machine boots but prints a warning
> > >about the unexpected PFN ranges. It boot-tested fine on a number of other
> > >machines (x86-32 x86-64 and ppc64).
> > >
> > ok, I'll test today if I have a chance. At least, I think I can test this
> > until Monday. but I have one concern (below)
> >
> I tested and found your patch doesn't work.
> It seems because all valid page struct is not initialized.
The fact I didn't calculate end_pfn properly as pointed out by Dave Hansen
didn't help either. If that was corrected, I'd be surprised if the patch
didn't work. If it is broken, it implies that arch-specific code is using
PFN ranges that do not contain valid memory - something I find surprising.
> (By pfn_valid(), a page struct is valid if it exists regardless of zones.)
>
> How about below ? I think this is simple.
> Tested and worked well.
>
This patch is fine. It checks the ranges passed in a less-invasive
fashion than the previous patch. Thanks
Acked-by: Mel Gorman <mel@csn.ul.ie>
> ==
> usemap must be initialized only when pfn is within zone.
> If not, it corrupts memory.
>
> After intialization, usemap is used for only pfn in valid range.
> (We have to init memmap even in invalid range.)
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> ---
> mm/page_alloc.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.25/mm/page_alloc.c
> ===================================================================
> --- linux-2.6.25.orig/mm/page_alloc.c
> +++ linux-2.6.25/mm/page_alloc.c
> @@ -2518,6 +2518,7 @@ void __meminit memmap_init_zone(unsigned
> struct page *page;
> unsigned long end_pfn = start_pfn + size;
> unsigned long pfn;
> + struct zone *z;
>
> for (pfn = start_pfn; pfn < end_pfn; pfn++) {
> /*
> @@ -2536,7 +2537,7 @@ void __meminit memmap_init_zone(unsigned
> init_page_count(page);
> reset_page_mapcount(page);
> SetPageReserved(page);
> -
> + z = page_zone(page);
> /*
> * Mark the block movable so that blocks are reserved for
> * movable at startup. This will force kernel allocations
> @@ -2546,7 +2547,9 @@ void __meminit memmap_init_zone(unsigned
> * the start are marked MIGRATE_RESERVE by
> * setup_zone_migrate_reserve()
> */
> - if ((pfn & (pageblock_nr_pages-1)))
> + if ((z->zone_start_pfn < pfn)
> + && (pfn < z->zone_start_pfn + z->spanned_pages)
> + && !(pfn & (pageblock_nr_pages-1)))
> set_pageblock_migratetype(page, MIGRATE_MOVABLE);
>
> INIT_LIST_HEAD(&page->lru);
> @@ -4460,6 +4463,8 @@ void set_pageblock_flags_group(struct pa
> pfn = page_to_pfn(page);
> bitmap = get_pageblock_bitmap(zone, pfn);
> bitidx = pfn_to_bitidx(zone, pfn);
> + VM_BUG_ON(pfn < zone->zone_start_pfn);
> + VM_BUG_ON(pfn >= zone->zone_start_pfn + zone->spanned_pages);
>
> for (; start_bitidx <= end_bitidx; start_bitidx++, value <<= 1)
> if (flags & value)
>
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2008-04-21 10:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48080706.50305@cn.fujitsu.com>
[not found] ` <48080930.5090905@cn.fujitsu.com>
2008-04-18 2:46 ` [PATCH] memcgroup: check and initialize page->cgroup in memmap_init_zone Shi Weihua
2008-04-18 3:04 ` KAMEZAWA Hiroyuki
2008-04-18 3:14 ` Shi Weihua
2008-04-18 3:14 ` Andrew Morton
2008-04-18 3:32 ` KAMEZAWA Hiroyuki
2008-04-18 5:09 ` KAMEZAWA Hiroyuki
2008-04-18 5:43 ` Shi Weihua
2008-04-18 5:57 ` KAMEZAWA Hiroyuki
2008-04-18 6:47 ` KAMEZAWA Hiroyuki
2008-04-18 3:37 ` Balbir Singh
2008-04-18 3:49 ` Shi Weihua
2008-04-18 12:12 ` [PATCH]Fix usemap for DISCONTIG/FLATMEM with not-aligned zone initilaization KAMEZAWA Hiroyuki
2008-04-18 16:15 ` Mel Gorman
2008-04-18 17:41 ` Dave Hansen
2008-04-18 17:25 ` kamezawa.hiroyu
2008-04-21 2:20 ` KAMEZAWA Hiroyuki
2008-04-21 10:12 ` Mel Gorman [this message]
2008-04-21 10:29 ` KAMEZAWA Hiroyuki
2008-04-21 11:56 ` Hugh Dickins
2008-04-22 1:40 ` [BUGFIX][PATCH] Fix usemap initialization v2 KAMEZAWA Hiroyuki
2008-04-22 10:12 ` Hugh Dickins
2008-04-23 1:45 ` KAMEZAWA Hiroyuki
2008-04-23 2:17 ` Shi Weihua
2008-04-23 4:46 ` [BUGFIX][PATCH] Fix usemap initialization v3 KAMEZAWA Hiroyuki
2008-04-23 6:19 ` Shi Weihua
2008-04-23 8:04 ` KAMEZAWA Hiroyuki
2008-04-23 12:46 ` Mel Gorman
2008-04-27 19:18 ` Andrew Morton
2008-04-27 19:30 ` Balbir Singh
2008-04-27 22:50 ` Hugh Dickins
2008-04-28 0:39 ` KAMEZAWA Hiroyuki
2008-04-21 13:02 ` Re: [PATCH]Fix usemap for DISCONTIG/FLATMEM with not-aligned zone initilaization kamezawa.hiroyu
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=20080421101231.GA629@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shiwh@cn.fujitsu.com \
--cc=xemul@openvz.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).