From: Michael.Kang <blackfin.kang@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: About resevation of kernel code and data section in e500 part.
Date: Tue, 16 Oct 2007 10:49:11 +0800 [thread overview]
Message-ID: <a7f827420710151949q33a1179dw540ae9c6da42b27c@mail.gmail.com> (raw)
Hi:
I have some confusions about where the page of kernel text
and data is reserved in linux source ? Hope get some hints here and
thanks in advance.
I had digged into some related code, but got no anwser:
1. in set_phys_avail [ arch/ppc/mm/init.c : 456] , it seems memory
used by kernel text and data is reserved for bootmem.
2. Then in memmap_init_zone [mm/page_alloc.c:1925] , all the page is
set reserved including the pages used by kernel text and data. And it
seems page->virtual in all the page is set here.
So my question is where the pages used by kernel text and data is set
to reserved in linux source?
-- Thanks
-- Michael.Kang
--
www.skyeye.org
reply other threads:[~2007-10-16 2:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a7f827420710151949q33a1179dw540ae9c6da42b27c@mail.gmail.com \
--to=blackfin.kang@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).