From: Jiri Slaby <jirislaby@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH 1/2] x86_64: fix mm.txt documentation
Date: Fri, 02 May 2008 10:47:36 +0200 [thread overview]
Message-ID: <481AD528.1090809@gmail.com> (raw)
In-Reply-To: <20080502083805.GR20451@one.firstfloor.org>
On 05/02/2008 10:38 AM, Andi Kleen wrote:
>> yep, the image was in a 128 MB chunk from which 88 MB was left empty and
>> modules started at the next 128 MB boundary. The largest image i ever
>> had was around 44MB, so i doubt it's an issue in practice. Mind doing a
>> patch that reinstates it, by lowering the 512 image size limit to 508
>> MB? [4MB should be more than enough in practice]
>
> Actually you could even limit to the exact know size of the kernel (rounded
> up to 2MB) after early boot. Then the protection would be even better and less
> aliasing to deal with for pageattr.c. Just invalidate the left over PMDs.
Doesn't cleanup_highmap() do that? ... so I guess we don't need the hole? Or do
we when we reach the limit to not go over to modules?
next prev parent reply other threads:[~2008-05-02 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 9:58 [PATCH 1/2] x86_64: fix mm.txt documentation Jiri Slaby
2008-05-01 9:58 ` [PATCH 2/2] x86_64: use PAGE_OFFSET in dump_pagetables Jiri Slaby
2008-05-02 7:33 ` Ingo Molnar
2008-05-02 7:22 ` [PATCH 1/2] x86_64: fix mm.txt documentation Ingo Molnar
2008-05-02 7:57 ` Jiri Slaby
2008-05-02 8:38 ` Andi Kleen
2008-05-02 8:47 ` Jiri Slaby [this message]
2008-05-02 8:00 ` Andi Kleen
2008-05-02 7:55 ` Jiri Slaby
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=481AD528.1090809@gmail.com \
--to=jirislaby@gmail.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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