From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Christian Ehrhardt <lk@c--e.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: New x86-Setup code breaks HVM-XEN boot
Date: Wed, 05 Sep 2007 14:06:05 +0100 [thread overview]
Message-ID: <1188997566.11625.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20070831075434.GF20195@genua.de>
On Fri, 2007-08-31 at 09:54 +0200, Christian Ehrhardt wrote:
> (XEN) (GUEST: 353) Detected Xen v3.0.3-1
I was unable to reproduce this problem on Xen 3.1.0 although I can't
immediately see a particular changeset which obviously fixed it. There
have been plenty of fixes to the emulator since 3.0.3 though so it's
worth trying a newer version.
In a later mail:
> 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.
The emulation of lgdt (in tools/firmware/vmxassist/vm86.c) looks sane
enough on first glance (i.e. it saves the base and length not the
pointer) although it isn't an area of the code I'm particularly familiar
with.
Ian.
prev parent reply other threads:[~2007-09-05 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 14:15 New x886-Setup " 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
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 [this message]
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=1188997566.11625.16.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--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
all inboxes | Powered by JetHome®