From: Jun Sun <jsun@mvista.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: memory for exception vectors
Date: Tue, 13 May 2003 09:52:44 -0700 [thread overview]
Message-ID: <20030513095244.B26990@mvista.com> (raw)
In-Reply-To: <20030513105145.D22288@ftp.linux-mips.org>; from ladis@linux-mips.org on Tue, May 13, 2003 at 10:51:45AM +0100
On Tue, May 13, 2003 at 10:51:45AM +0100, Ladislav Michl wrote:
> On Mon, May 12, 2003 at 10:44:08AM -0700, Jun Sun wrote:
> > On Mon, May 12, 2003 at 11:56:41AM +0100, Ladislav Michl wrote:
> > > Could anyone tell me where is space for exception vectors reserved? Many boards
> > > (for example Alchemy Pb1000, Galileo EV96100 or Galileo EV64120A) simply
> > > registers all available RAM with add_memory_region call, but I didn't find code
> > > which reserves first 0x200 (on most CPUs) for exceptions vectors anywhere. I'd
> > > guess there is something obvious what I'm missing. Can you help me to see it?
> >
> > Kernel only uses memory after the end of kernel image. In that sense, all
> > memory before LOADADDR (see arch/mips/Makefile) is reserved.
>
> I'm afraid, I didn't find any code which does what you're describing here.
> But in arch/mips/mm/init.c is function setup_zero_pages which allocates
> first (or first eight if CPU has VCE) page(s). Does it do the trick?
>
Now you are really pushing me. :)
I figured that out a while back. I think you can find answers in
arch/mips/kernel/setup.c,
start_pfn = PFN_UP(__pa(&_end));
I think zero pages are allocated so that all future read-only zero-filled
pages can be mapped to them. They are allocated at the beginning of
start_pfn, which is also after kernel image.
Jun
next prev parent reply other threads:[~2003-05-13 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 10:56 memory for exception vectors Ladislav Michl
2003-05-12 17:44 ` Jun Sun
2003-05-13 9:51 ` Ladislav Michl
2003-05-13 16:52 ` Jun Sun [this message]
2003-05-13 17:11 ` Ladislav Michl
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=20030513095244.B26990@mvista.com \
--to=jsun@mvista.com \
--cc=ladis@linux-mips.org \
--cc=linux-mips@linux-mips.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