From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use correct x86 reboot vector
Date: Mon, 12 May 2003 17:36:23 +0200 (MET DST) [thread overview]
Message-ID: <Pine.GSO.3.96.1030512172208.19804B-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <m1smrl5mbw.fsf@frodo.biederman.org>
On 11 May 2003, Eric W. Biederman wrote:
> There is some software at least that knows the difference. I have seen short
> jumps in a couple of BIOS's. But a reset is very different from a
> reboot. As memory must be reinitialized etc. So I think going to
> 0xffff0000:0xfff0 would be a very bad idea if the intent is to get a
> reliable reboot.
You may change a bit in the i8042 controller to make a BIOS assume that's
a cold boot. The bit is zeroed (IIRC; apply a complement if my memory is
bad) upon a system RESET that's propagated to the i8042 (i.e. a power-on
or a button reset, but not a triple-fault or i8042 output port or port
0x92, etc. one). The bit is set to one by a BIOS during POST and never
zeroed afterwards, but it's r/w, so there is no problem to clear it if
needed. This should be quite a reliable way to reboot as a BIOS is
assumed to initialize hardware from scratch (regardless of the reset
vector used).
This assumes 100% PC/AT compatibility, of course, which need not be true
these days any longer.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-05-12 15:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 2:56 [PATCH] Use correct x86 reboot vector Andi Kleen
2003-05-10 3:35 ` CaT
2003-05-10 3:58 ` H. Peter Anvin
2003-05-10 14:49 ` Alan Cox
2003-05-10 16:17 ` Jamie Lokier
2003-05-10 18:47 ` Jos Hulzink
2003-05-11 18:01 ` Eric W. Biederman
2003-05-11 17:24 ` Alan Cox
2003-05-11 19:04 ` Eric W. Biederman
2003-05-12 5:48 ` [PATCH] always shutdown on the bootstrap processor Eric W. Biederman
2003-05-10 16:15 ` [PATCH] Use correct x86 reboot vector Jamie Lokier
2003-05-10 17:09 ` Randy.Dunlap
2003-05-10 19:41 ` Jos Hulzink
2003-05-10 18:10 ` Jamie Lokier
2003-05-10 20:55 ` Jos Hulzink
2003-05-11 3:50 ` Linus Torvalds
2003-05-11 9:37 ` Jos Hulzink
2003-05-11 14:01 ` Jamie Lokier
2003-05-11 17:38 ` Davide Libenzi
2003-05-11 17:56 ` Eric W. Biederman
2003-05-11 18:23 ` Davide Libenzi
2003-05-11 19:12 ` Eric W. Biederman
2003-05-12 15:36 ` Maciej W. Rozycki [this message]
2003-05-13 6:35 ` H. Peter Anvin
2003-05-11 18:38 ` Linus Torvalds
2003-05-11 19:00 ` Matt Mackall
2003-05-11 19:16 ` Eric W. Biederman
2003-05-12 1:07 ` H. Peter Anvin
2003-05-11 19:10 ` Eric W. Biederman
2003-05-11 18:43 ` Christer Weinigel
2003-05-11 20:22 ` wingel
2003-05-11 20:26 ` Davide Libenzi
2003-05-11 17:54 ` Eric W. Biederman
2003-05-13 12:49 Chuck Ebbert
2003-05-13 18:45 ` H. Peter Anvin
2003-05-13 19:04 ` Richard B. Johnson
2003-05-13 19:27 ` 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=Pine.GSO.3.96.1030512172208.19804B-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=davidel@xmailserver.org \
--cc=ebiederm@xmission.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;
as well as URLs for NNTP newsgroup(s).