From: Werner Almesberger <wa@almesberger.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andy Pfiffer <andyp@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
fastboot@osdl.org
Subject: Re: [Fastboot] [CFT] kexec syscall for 2.5.43 (linux booting linux)
Date: Tue, 22 Oct 2002 05:30:05 -0300 [thread overview]
Message-ID: <20021022053005.F1421@almesberger.net> (raw)
In-Reply-To: <m13cqzumx3.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Mon, Oct 21, 2002 at 10:18:00PM -0600
Eric W. Biederman wrote:
> Oh, wait as I recall bootimg simply copies the BIOS results
> from the current kernel to the freshly booted kernel, so it skips
> the BIOS calls altogether.
Yes, I don't trust the BIOS very much under normal conditions,
so I wouldn't even dream of running it with a largely undefined
system state. I'm actually quite surprised that kexec has so
few problems doing that :-)
In any case, since the kexec kernel code is more or less just a
generic loader, this is something you can always decide to
change in user space. The only thing bootimg did that kexec
doesn't do is to explicitly mark BIOS-provided data tables
(mainly SMP stuff) as reserved so that they won't be
overwritten. But it seems that mpparse.c now reserves that
already, so kexec should be fine.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-10-22 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:59 [CFT] kexec syscall for 2.5.43 (linux booting linux) Eric W. Biederman
[not found] ` <20021018173248.E14894@almesberger.net>
[not found] ` <m1bs5rz1d6.fsf@frodo.biederman.org>
[not found] ` <20021018231540.C7951@almesberger.net>
[not found] ` <20021019025309.A24579@almesberger.net>
[not found] ` <m17kgfyltc.fsf@frodo.biederman.org>
[not found] ` <20021019040600.D7951@almesberger.net>
2002-10-19 9:34 ` Eric W. Biederman
2002-10-19 17:18 ` Werner Almesberger
2002-10-19 17:37 ` Eric W. Biederman
2002-10-21 23:11 ` [Fastboot] " Andy Pfiffer
2002-10-22 4:18 ` Eric W. Biederman
2002-10-22 6:04 ` Eric W. Biederman
2002-10-22 8:33 ` Eric W. Biederman
2002-10-22 3:57 ` Rob Landley
2002-10-22 14:48 ` Eric W. Biederman
2002-10-22 16:02 ` Eric W. Biederman
2002-10-22 16:27 ` erich
2002-10-23 2:23 ` Eric W. Biederman
2002-10-22 16:30 ` erich
2002-10-22 23:27 ` Andy Pfiffer
2002-10-22 23:32 ` Andy Pfiffer
2002-10-22 8:30 ` Werner Almesberger [this message]
2002-10-22 8:55 ` Eric W. Biederman
2002-10-22 23:17 ` Andy Pfiffer
2002-10-23 6:29 ` Eric W. Biederman
2002-10-23 17:11 ` Andy Pfiffer
2002-10-24 17:10 ` Eric W. Biederman
2002-10-28 7:45 ` Kasper Dupont
2002-10-28 8:24 ` Eric W. Biederman
2002-10-28 8:48 ` Kasper Dupont
2002-10-28 17:14 ` 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=20021022053005.F1421@almesberger.net \
--to=wa@almesberger.net \
--cc=VANDROVE@vc.cvut.cz \
--cc=andyp@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.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