From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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>,
Eric Biederman <ebiederm@xmission.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)
Date: Mon, 5 Nov 2007 09:15:29 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.999.0711050842360.15101@woody.linux-foundation.org> (raw)
In-Reply-To: <200711050358.lA53wlho003349@tazenda.hos.anvin.org>
On Sun, 4 Nov 2007, H. Peter Anvin wrote:
>
> H. Peter Anvin (2):
> x86 setup: add a near jump to serialize %cr0 on 386/486
> x86 setup: set %ebx == %ebp == %edi == 0 on protected mode entry
Ok, I'm obviously happier, but I have to admit that the original code was
safer than the new code. It did both the short jump and the far jump
before reloading any segments.
So I suspect the new code _works_ fine, but it's simply not as
fundamentally safe as the old code was.
The old code did do some instructions in between the short jump and the
far jump, but they were all the kind of instructions that didn't care
about the PE bit: there was a _read_ of the segment descriptor value, but
that's mode-independent (it's only the writes that matter), and the other
instructions were bog-standard integer instructions.
So I would actually prefer some additional safety, with something like
the appended..
This is TOTALLY UNTESTED! I checked with objdump that the result looks
roughly ok, but I didn't really think through the segment base address in
that long jump thing. Do we have the difference between flat mode and the
16-bit bootup mode in some better way?
Hmm?
Linus
--
arch/x86/boot/pmjump.S | 25 +++++++++++++++++--------
1 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/arch/x86/boot/pmjump.S b/arch/x86/boot/pmjump.S
index fa6bed1..587dc04 100644
--- a/arch/x86/boot/pmjump.S
+++ b/arch/x86/boot/pmjump.S
@@ -29,7 +29,11 @@
*/
protected_mode_jump:
movl %edx, %esi # Pointer to boot_params table
- movl %eax, 2f # Patch ljmpl instruction
+
+ xorl %ecx, %ecx # add data segment offset to
+ movw %ds, %cx # the "in_32_bit_mode" thing.
+ shll $4, %ecx
+ addl %ecx, 2f
movw $__BOOT_DS, %cx
xorl %ebx, %ebx # Per the 32-bit boot protocol
@@ -42,15 +46,20 @@ protected_mode_jump:
jmp 1f # Short jump to serialize on 386/486
1:
- movw %cx, %ds
- movw %cx, %es
- movw %cx, %fs
- movw %cx, %gs
- movw %cx, %ss
-
# Jump to the 32-bit entrypoint
.byte 0x66, 0xea # ljmpl opcode
-2: .long 0 # offset
+2: .long in_32_bit_mode # offset
.word __BOOT_CS # segment
.size protected_mode_jump, .-protected_mode_jump
+
+ .code32
+ .align 4
+in_32_bit_mode:
+ mov %cx, %ds
+ mov %cx, %es
+ mov %cx, %fs
+ mov %cx, %gs
+ mov %cx, %ss
+ jmp *%eax
+ .size in_32_bit_mode, .-in_32_bit_mode
next prev parent reply other threads:[~2007-11-05 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 2:16 H. Peter Anvin
2007-11-05 3:58 ` H. Peter Anvin
2007-11-05 17:15 ` Linus Torvalds [this message]
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
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=alpine.LFD.0.999.0711050842360.15101@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®