From: Dave Hansen <dave@linux.vnet.ibm.com>
To: C Michael Sundius <Michael.sundius@sciatl.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
linux-mm@kvack.org, msundius@sundius.com
Subject: Re: Turning on Sparsemem
Date: Tue, 05 Aug 2008 14:56:24 -0700 [thread overview]
Message-ID: <1217973384.10907.70.camel@nimitz> (raw)
In-Reply-To: <4898C88E.9070006@sciatl.com>
On Tue, 2008-08-05 at 14:39 -0700, C Michael Sundius wrote:
> Hi Andy and Dave,
>
> I turned on sparsemem as you described before. I am crashing in
> the mem_init() function when I try a call to pfn_to_page().
>
> I've noticed that that macro uses the sparsemem macro
> __pfn_to_section(pfn) and
> that intern calls __nr_to_section(nr). That finally looks at the
> mem_section[] variable.
> well.. this returns NULL since it seems as though my mem_section[] array
> looks
> to be not initialized correctly.
>
> QUESTION: where does this array get initialized. I've looked through the
> code and
> can't seem to see how that is initialized.
My first guess is that you're missing a call to sparse_init() in your
architecture-specific code. On x86_32, we do that in paging_init(),
just before zone_sizes_init() (arch/x86/mm/init_32.c).
Before you call this, you'll also have to call memory_present(...) on
the memory that you do have. But, you should probably already have done
that.
> recall I'm using mips32 processor, but I've looked in all the processors.
> it seems as though sparse_init() and memory present() both use
> __nr_to_section()
> and thus would require mem_section[] to be set up already.
__nr_to_section() is special. It takes a section number and just gives
you back the 'struct mem_section'. It doesn't actually look into that
mem_section and make sure it is valid, it just locates the data
structure.
-- Dave
--
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-08-05 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 18:11 sparcemem or discontig? C Michael Sundius
2008-07-29 21:51 ` Dave Hansen
2008-07-30 9:35 ` Andy Whitcroft
2008-07-30 16:23 ` C Michael Sundius
2008-07-30 16:29 ` Dave Hansen
2008-08-05 21:39 ` Turning on Sparsemem C Michael Sundius
2008-08-05 21:56 ` Dave Hansen [this message]
2008-08-05 22:04 ` C Michael Sundius
2008-08-05 22:19 ` Dave Hansen
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=1217973384.10907.70.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=Michael.sundius@sciatl.com \
--cc=apw@shadowen.org \
--cc=linux-mm@kvack.org \
--cc=msundius@sundius.com \
/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.