linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Matt Mackall <mpm@selenic.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	Jamie Lokier <jamie@shareable.org>, Jos Hulzink <josh@stack.nl>,
	Andi Kleen <ak@muc.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use correct x86 reboot vector
Date: 11 May 2003 13:16:26 -0600	[thread overview]
Message-ID: <m1of295m5x.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030511190023.GC9173@waste.org>

Matt Mackall <mpm@selenic.com> writes:

> There's a missing piece of behavior here that's probably fatal.
> Namely, the next time the CS descriptor is loaded, even with the same
> value, the high bits are lost. So, for example, if you're running BIOS
> out of ROM, decompressing it into the top of 20-bit address space,
> then long jumping to your uncompressed code, you don't want to find
> yourself back in ROM.
> 
> Perhaps there's a trick that can be played with loading the descriptor
> into CS and then clearing the descriptor table without flushing, but it
> sounds rather dubious..

If PE is really disabled that should bit should come for free.  And it
is why it is so hard to fake this behavior.

Eric

  reply	other threads:[~2003-05-11 19:07 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
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 [this message]
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=m1of295m5x.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=ak@muc.de \
    --cc=davidel@xmailserver.org \
    --cc=jamie@shareable.org \
    --cc=josh@stack.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).