From: ebiederm@xmission.com (Eric W. Biederman)
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
linux-kernel@vger.kernel.org,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: kexec reboot code buffer
Date: 28 Jan 2003 00:28:04 -0700 [thread overview]
Message-ID: <m1isw968e3.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030128071826.GI780@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> writes:
> On Tue, Jan 28, 2003 at 12:04:19AM -0700, Eric W. Biederman wrote:
> > I agree that lowmem for the common case is fine. For kexec on panic,
> > and a some weird cases using high mem is beneficial. I don't have
> > a problem with changing it back to just lowmem for the time being.
>
> Well, there is the bit about dropping the PAE bit from %cr4 too.
Already done, it actually doesn't byte me until the next kernel starts
to execute, as we only set and not clear the PAE bit during bootup.
> Seriously, just plop down the fresh zone type and all will be well.
> It's really incredibly easy.
I will certainly take a look, tracing through that code can get a little
hairy.
Eric
next prev parent reply other threads:[~2003-01-28 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E31AC58.2020802@us.ibm.com>
2003-01-25 14:16 ` kexec reboot code buffer Eric W. Biederman
2003-01-27 21:55 ` Dave Hansen
2003-01-27 22:03 ` Martin J. Bligh
2003-01-28 0:10 ` William Lee Irwin III
2003-01-28 7:24 ` Eric W. Biederman
2003-01-28 16:15 ` Martin J. Bligh
2003-01-29 15:41 ` Eric W. Biederman
2003-01-29 16:17 ` Martin J. Bligh
2003-01-28 7:04 ` Eric W. Biederman
2003-01-28 7:18 ` William Lee Irwin III
2003-01-28 7:28 ` Eric W. Biederman [this message]
2003-01-28 7:31 ` William Lee Irwin III
2003-01-28 15:21 ` Eric W. Biederman
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=m1isw968e3.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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