From: Ladislav Michl <ladis@linux-mips.org>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: memory for exception vectors
Date: Tue, 13 May 2003 18:11:52 +0100 [thread overview]
Message-ID: <20030513181152.A5160@ftp.linux-mips.org> (raw)
In-Reply-To: <20030513095244.B26990@mvista.com>; from jsun@mvista.com on Tue, May 13, 2003 at 09:52:44AM -0700
On Tue, May 13, 2003 at 09:52:44AM -0700, Jun Sun wrote:
[snip]
> 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));
Strange I read that file many times, but for yet unknown reason never noticed
__pa(&_end). That's what I call selective blindness :)
> 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.
Thanks a lot for explanation, now I'm sure that MC based memory probing for
IP22 will not break anything. Patch will come tomorrow.
Ladis
prev parent reply other threads:[~2003-05-13 17:11 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
2003-05-13 17:11 ` Ladislav Michl [this message]
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=20030513181152.A5160@ftp.linux-mips.org \
--to=ladis@linux-mips.org \
--cc=jsun@mvista.com \
--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