From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH 1/3] mm, nobootmem: fix wrong usage of max_low_pfn
Date: Tue, 19 Mar 2013 15:42:47 +0900 [thread overview]
Message-ID: <20130319064247.GH8858@lge.com> (raw)
In-Reply-To: <20130319062522.GG8858@lge.com>
On Tue, Mar 19, 2013 at 03:25:22PM +0900, Joonsoo Kim wrote:
> On Mon, Mar 18, 2013 at 10:47:41PM -0700, Yinghai Lu wrote:
> > On Mon, Mar 18, 2013 at 10:15 PM, Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
> > > max_low_pfn reflect the number of _pages_ in the system,
> > > not the maximum PFN. You can easily find that fact in init_bootmem().
> > > So fix it.
> >
> > I'm confused. for x86, we have max_low_pfn defined in ...
>
> Below is queote from Russell King in 'https://lkml.org/lkml/2013/3/13/123'
>
>
> Now, max_low_pfn is initialized this way:
>
> /**
> * init_bootmem - register boot memory
> * @start: pfn where the bitmap is to be placed
> * @pages: number of available physical pages
> *
> * Returns the number of bytes needed to hold the bitmap.
> */
> unsigned long __init init_bootmem(unsigned long start, unsigned long pages)
> {
> max_low_pfn = pages;
> min_low_pfn = start;
> return init_bootmem_core(NODE_DATA(0)->bdata, start, 0, pages);
> }
> So, min_low_pfn is the PFN offset of the start of physical memory (so
> 3GB >> PAGE_SHIFT) and max_low_pfn ends up being the number of pages,
> _not_ the maximum PFN value
>
> So, if physical address doesn't start at 0, max_low_pfn doesn't represent
> the maximum PFN value. This is a case for ARM.
>
> >
> > #ifdef CONFIG_X86_32
> > /* max_low_pfn get updated here */
> > find_low_pfn_range();
> > #else
> > num_physpages = max_pfn;
> >
> > check_x2apic();
> >
> > /* How many end-of-memory variables you have, grandma! */
> > /* need this before calling reserve_initrd */
> > if (max_pfn > (1UL<<(32 - PAGE_SHIFT)))
> > max_low_pfn = e820_end_of_low_ram_pfn();
> > else
> > max_low_pfn = max_pfn;
> >
> > and under max_low_pfn is bootmem.
> >
> > >
> > > Additionally, if 'start_pfn == end_pfn', we don't need to go futher,
> > > so change range check.
> > >
> > > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> > >
> > > diff --git a/mm/nobootmem.c b/mm/nobootmem.c
> > > index 5e07d36..4711e91 100644
> > > --- a/mm/nobootmem.c
> > > +++ b/mm/nobootmem.c
> > > @@ -110,9 +110,9 @@ static unsigned long __init __free_memory_core(phys_addr_t start,
> > > {
> > > unsigned long start_pfn = PFN_UP(start);
> > > unsigned long end_pfn = min_t(unsigned long,
> > > - PFN_DOWN(end), max_low_pfn);
> > > + PFN_DOWN(end), min_low_pfn);
> >
> > what is min_low_pfn ? is it 0 for x86?
>
> My implementation is totally wrong. :)
> min_low_pfn is not proper value for this purpose.
>
> I will fix it.
> Sorry for noise.
>
> Thanks.
How about using "memblock.current_limit"?
unsigned long end_pfn = min_t(unsigned long, PFN_DOWN(end),
memblock.current_limit);
Thanks.
>
> >
> > Thanks
> >
> > Yinghai
> >
> > --
> > 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>
>
> --
> 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>
--
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:[~2013-03-19 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 5:15 [PATCH 1/3] mm, nobootmem: fix wrong usage of max_low_pfn Joonsoo Kim
2013-03-19 5:16 ` [PATCH 2/3] mm, nobootmem: clean-up of free_low_memory_core_early() Joonsoo Kim
2013-03-19 5:50 ` Joonsoo Kim
2013-03-19 5:51 ` Yinghai Lu
2013-03-19 5:58 ` Joonsoo Kim
2013-03-19 5:16 ` [PATCH 3/3] mm, nobootmem: do memset() after memblock_reserve() Joonsoo Kim
2013-03-19 5:53 ` Yinghai Lu
2013-03-19 5:58 ` Joonsoo Kim
2013-03-19 5:47 ` [PATCH 1/3] mm, nobootmem: fix wrong usage of max_low_pfn Yinghai Lu
2013-03-19 6:25 ` Joonsoo Kim
2013-03-19 6:42 ` Joonsoo Kim [this message]
2013-03-19 7:35 ` Yinghai Lu
2013-03-19 8:07 ` Joonsoo Kim
2013-03-20 20:18 ` Sam Ravnborg
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=20130319064247.GH8858@lge.com \
--to=iamjoonsoo.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=yinghai@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 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).