From: "H. Peter Anvin" <hpa@zytor.com>
To: Christian Ehrhardt <lk@c--e.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New x86-Setup code breaks HVM-XEN boot
Date: Tue, 04 Sep 2007 07:16:47 +0100 [thread overview]
Message-ID: <46DCF84F.1010302@zytor.com> (raw)
In-Reply-To: <20070903183237.GA1208@genua.de>
Christian Ehrhardt wrote:
>
> I took the trouble to bisect (manually) exactly which change in the new
> boot code triggers this problem.
>
> The problem is with the lgdt instruction. Apparently XEN does not keep
> the contents of the 48-bit gdt_48 data structure that is passed to lgdt
> in the XEN machine state. Instead it appears to save the _address_ of the
> 48-bit descriptor somewhere. Unfortunately this data happens to reside on the
> stack and is probably no longer availiable at the time of the actual
> protected mode jump.
>
> This is most likely a XEN-bug but given that there is a on line patch
> to work around this problem, the linux kernel should probably do this.
> My fix is to make the gdt_48 description in setup_gdt static (in
> setup_idt this is already the case). This allows the kernel to boot under
> XEN-hvm again.
Would indeed be a Xen bug, and a pretty serious one too. Quite frankly,
it reflects some pretty fundamental misconceptions about how x86 works.
>
> Sometimes it is a bit disappointing if quite some debuggin work results
> in a on line patch :-) Pleae consider applying.
>
LOL, well, that's usually a good thing.
-hpa
next prev parent reply other threads:[~2007-09-04 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 14:15 New x886-Setup code breaks HVM-XEN boot Christian Ehrhardt
2007-08-30 14:49 ` H. Peter Anvin
2007-09-03 18:32 ` New x86-Setup " Christian Ehrhardt
2007-09-04 6:16 ` H. Peter Anvin [this message]
2007-08-30 19:04 ` New x886-Setup " Jeremy Fitzhardinge
2007-08-31 7:54 ` New x86-Setup " Christian Ehrhardt
2007-08-31 14:20 ` H. Peter Anvin
2007-09-05 13:06 ` Ian Campbell
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=46DCF84F.1010302@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@c--e.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