From: Andi Kleen <andi@firstfloor.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Trolle Selander <trolle.selander@gmail.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [RFC] More fp instructions for realmode emulation (Enables booting OS/2 as a HVM guest on Intel/VT hardware)
Date: Mon, 3 Mar 2008 17:59:29 +0100 [thread overview]
Message-ID: <20080303165929.GC9853@one.firstfloor.org> (raw)
In-Reply-To: <C3F1C324.1D5A0%keir.fraser@eu.citrix.com>
On Mon, Mar 03, 2008 at 03:00:52PM +0000, Keir Fraser wrote:
> On 3/3/08 14:52, "Andi Kleen" <andi@firstfloor.org> wrote:
>
> >> Intel SDM Volume 1 Section 8.6 (?X87 FPU Exception Synchronization?) is very
> >> helpful in this regard. It confirms my suspicions, that we will need to wrap
> >> the FPU inline asms in some fixup glue. The only exceptions to this rule are
> >
> > Yes you definitely need to. That was a kernel crash bug on native Linux
> > some time ago...
> >
> > Also you need to do the same for any FXSAVEs/FXRSTORs if you haven't already.
>
> FXSAVE/FXRSTOR do not flush pending FPU exceptions, right?
Yes they do not, but there are other ways to make them #GP
-Andi
next prev parent reply other threads:[~2008-03-03 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 22:14 [PATCH] [RFC] More fp instructions for realmode emulation (Enables booting OS/2 as a HVM guest on Intel/VT hardware) Trolle Selander
2008-03-01 8:46 ` Keir Fraser
2008-03-01 9:18 ` Keir Fraser
2008-03-03 12:18 ` Trolle Selander
2008-03-03 12:21 ` Keir Fraser
2008-03-03 14:52 ` Andi Kleen
2008-03-03 15:00 ` Keir Fraser
2008-03-03 16:59 ` Andi Kleen [this message]
2008-03-03 17:30 ` Keir Fraser
2008-03-03 18:11 ` Andi Kleen
2008-03-04 10:13 ` Keir Fraser
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=20080303165929.GC9853@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=keir.fraser@eu.citrix.com \
--cc=trolle.selander@gmail.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.