From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time.
Date: 20 Dec 2001 09:39:02 -0700 [thread overview]
Message-ID: <m1n10dvobd.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200112181605.KAA00820@tomcat.admin.navo.hpc.mil> <m18zbzwp34.fsf@frodo.biederman.org> <3C205FBC.60307@zytor.com> <m1zo4fursh.fsf@frodo.biederman.org> <9vrlef$mat$1@cesium.transmeta.com> <m1r8pqv1w3.fsf@frodo.biederman.org> <3C218BF3.6010603@zytor.com>
In-Reply-To: <3C218BF3.6010603@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> My comment was mostly that there is a persistent myth that you can't use the x86
> firmware from protected mode. You can't, directly, but you can get the
> functionality through other means. This is hardly a new technique; in fact,
> it's very similar to the DOS extenders of old times; in fact, it's somewhat
> simpler.
Agreed. And to completely dispel the myth. Etherboot has been doing
something similar for years. It disables interrupts in 32bit mode so
it doesn't have quite as much work to do but otherwise it is pretty
much the same picture.
I finally tracked down the reason why Setup.S is run in real mode,
instead of being called from protected mode. And that is in extremely
hostile environments (like loadlin works in) loading the kernel wrecks
the firmware callbacks. So you must do your BIOS calls as a special
case before you switch to protected mode.
Eric
next prev parent reply other threads:[~2001-12-20 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 16:05 Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time Jesse Pollard
[not found] ` <m1r8prwuv7.fsf@frodo.biederman.org>
[not found] ` <3C204282.3000504@zytor.com>
[not found] ` <m1itb3wsld.fsf@frodo.biederman.org>
[not found] ` <3C2052C0.2010700@zytor.com>
2001-12-19 9:12 ` Eric W. Biederman
2001-12-19 9:37 ` H. Peter Anvin
2001-12-19 15:57 ` Eric W. Biederman
2001-12-20 3:20 ` H. Peter Anvin
2001-12-20 6:31 ` Eric W. Biederman
2001-12-20 6:57 ` H. Peter Anvin
2001-12-20 16:39 ` Eric W. Biederman [this message]
2001-12-20 18:35 ` H. Peter Anvin
2001-12-21 16:57 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-12-17 22:10 Booting a modular kernel through a multiple streams file Grover, Andrew
2001-12-18 15:26 ` Booting a modular kernel through a multiple streams file / Making Linux multiboot capable and grub loading kernel modules at boot time Christian Koenig
2001-12-18 18:32 ` H. Peter Anvin
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=m1n10dvobd.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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