From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Mikael Petterson <mikpe@it.uu.se>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)
Date: Mon, 05 Nov 2007 13:28:59 -0800 [thread overview]
Message-ID: <472F8B1B.2070402@zytor.com> (raw)
In-Reply-To: <m1ir4g9yy7.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
>
> I'm just saying be liberal in what you accept and conservative in what
> you send.
>
Absolutely.
> Making the entire process well defined is useful so things don't break
> unnecessarily, and the maintainers of the pieces of software that use
> the interface know what they can reliably get away with and what is
> just luck.
>
> Currently using the 32-bit entry point reliably requires:
> %cs to be set.
> %esi to be set.
> %ebx be set to 0.
> %gdt to be set and have:
> 0x10 a 32bit 4G code segment with base of 0
> 0x18 a 32bit 4G data segment with base of 0
>
Actually, I suspect the currently code will handle %ebx with any value,
but some older kernels might not handle that correctly.
> With the latest generation of the boot protocol if KEEP_SEGMENTS
> is set then it is only required that the data segments %ds, %es, %fs,
> %gs and %ss be initialized to a valid value.
>
> I have no problem with code providing more then what is required
> above, and in fact I think it is likely a good thing.
>
> For future expansion of the protocol things will go easiest if
> we don't add additional requirements to the list above, as that
> is all that I think all current boot loaders provide.
Specifying now that unused GPRs should be zeroed will allow for changes
if and when we need it. It's an easy requirement to fulfill, so boot
loader authors can put it through the pipe now. Then, if we find
ourselves in a corner in the future, we have a possible out.
> Anyway this is getting off topic. So far the changes to pmjump.S
> look to be going well.
Thanks. I just pushed two more patches to the git tree; one to do the
paranoia thing, and one to initialize LDTR and TR; the latter is for the
benefit of Intel VT and is not required for correctness, but it should
be able to speed up booting slightly on VT-based hardware.
See:
http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-x86setup.git;a=log;h=for-linus
-hpa
next prev parent reply other threads:[~2007-11-05 21:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 2:16 [GIT PULL] x86 setup: correct booting on 486 (revised) H. Peter Anvin
2007-11-05 3:58 ` H. Peter Anvin
2007-11-05 17:15 ` Linus Torvalds
2007-11-05 17:56 ` H. Peter Anvin
2007-11-05 18:12 ` Linus Torvalds
2007-11-05 18:32 ` H. Peter Anvin
2007-11-05 18:36 ` Linus Torvalds
2007-11-05 20:21 ` Eric W. Biederman
2007-11-05 20:31 ` H. Peter Anvin
2007-11-05 20:51 ` Jeremy Fitzhardinge
2007-11-05 21:06 ` H. Peter Anvin
2007-11-06 0:59 ` Jeremy Fitzhardinge
2007-11-06 1:11 ` H. Peter Anvin
2007-11-06 1:18 ` Jeremy Fitzhardinge
2007-11-06 1:31 ` H. Peter Anvin
2007-11-06 16:17 ` Jeremy Fitzhardinge
2007-11-06 16:27 ` H. Peter Anvin
2007-11-06 16:55 ` Jeremy Fitzhardinge
2007-11-06 17:00 ` H. Peter Anvin
2007-11-06 17:09 ` Eric W. Biederman
2007-11-06 17:57 ` H. Peter Anvin
2007-11-06 18:27 ` Eric W. Biederman
2007-11-06 18:41 ` H. Peter Anvin
2007-11-06 17:04 ` Eric W. Biederman
2007-11-05 21:14 ` Eric W. Biederman
2007-11-05 21:28 ` H. Peter Anvin [this message]
2007-11-05 21:58 ` 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=472F8B1B.2070402@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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