From: Chris Wright <chrisw@sous-sol.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Zachary Amsden <zach@vmware.com>,
Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Crash while mapping memory in pagetable_init() (Was: Re: .config)
Date: Fri, 13 Apr 2007 17:10:35 -0700 [thread overview]
Message-ID: <20070414001035.GR10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <461FF09D.4020902@goop.org>
* Jeremy Fitzhardinge (jeremy@goop.org) wrote:
> Subject: i386: map enough initial memory to create lowmem mappings
>
> head.S creates the very initial pagetable for the kernel. This just
> maps enough space for the kernel itself, and an allocation bitmap.
> The amount of mapped memory is rounded up to 4Mbytes, and so this
> typically ends up mapping 8Mbytes of memory.
>
> When booting, pagetable_init() needs to create mappings for all
> lowmem, and the pagetables for these mappings are allocated from the
> free pages around the kernel in low memory. If the number of
> pagetable pages + kernel size exceeds head.S's initial mapping, it
> will end up faulting on an unmapped page. This will only happen with
> specific combinations of kernel size and memory size.
>
> This patch makes sure that head.S also maps enough space to fit the
> kernel pagetables as well as the kernel itself. It ends up using an
> additional two pages of unreclaimable memory.
Yup, fixes it up here, nice catch.
Acked-by: Chris Wright <chrisw@sous-sol.org>
next prev parent reply other threads:[~2007-04-14 0:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070413174913.GA25234@ezr.goop.org>
[not found] ` <20070413183841.GP10574@sequoia.sous-sol.org>
[not found] ` <20070413190552.GQ10574@sequoia.sous-sol.org>
[not found] ` <461FD97B.1010203@goop.org>
2007-04-13 20:09 ` Crash while mapping memory in pagetable_init() (Was: Re: .config) Zachary Amsden
2007-04-13 20:12 ` Jeremy Fitzhardinge
2007-04-13 20:26 ` H. Peter Anvin
2007-04-13 20:27 ` Jeremy Fitzhardinge
2007-04-13 20:32 ` H. Peter Anvin
2007-04-13 20:36 ` Jeremy Fitzhardinge
2007-04-13 20:42 ` H. Peter Anvin
2007-04-13 21:05 ` Jeremy Fitzhardinge
2007-04-13 21:12 ` H. Peter Anvin
2007-04-14 0:10 ` Chris Wright [this message]
2007-04-13 20:37 ` H. Peter Anvin
2007-04-13 21:07 ` Zachary Amsden
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=20070414001035.GR10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox