From: Kevin Wolf <mail@kevin-wolf.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] x86: Fix exceptions for fxsave/fxrstor
Date: Sun, 4 Oct 2009 22:43:54 +0200 [thread overview]
Message-ID: <200910042243.54712@kevin-wolf.de> (raw)
In-Reply-To: <20091004100516.GN6691@hall.aurel32.net>
Am Sonntag, 4. Oktober 2009 12:05 schrieb Aurelien Jarno:
> On Fri, Oct 02, 2009 at 10:28:57PM +0200, Kevin Wolf wrote:
> > This patch corrects the following aspects of exception generation in
> > fxsave/fxrstor:
> >
> > * Generate #GP if the operand is not aligned to a 16 byte boundary
>
> Agreed.
>
> > * Generate #UD if the LOCK prefix is used
>
> Agreed.
>
> > * For CR0.EM = 1 #NM is generated, not #UD
>
> This does not match the Intel manual:
> | #NM If CR0.TS[bit 3] = 1.
> |
> | #UD If CR0.EM[bit 2] = 1.
> | If CPUID.01H:EDX.FXSR[bit 24] = 0.
> | If the LOCK prefix is used.
> |
Hm, you seem to have a different Intel manual. In my copy the CR0.EM part
still belongs to #NM. Also, I ran my test code in KVM for comparision and it
did generate an #NM (on two different machines, one Intel, one AMD), so I'm
quite sure this is right (well, at least not completely wrong).
On the other hand, I just had a look at the AMD documentation and it seems to
support your version... So while my hardware suggests that #NM is right, I'm
not going to insist on it. Maybe there is some hardware that actually does
generate #UD.
If you don't like to commit this part of the fix despite my explanation, just
let me know and I'll resend the patch without it.
Kevin
next prev parent reply other threads:[~2009-10-04 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 20:28 [Qemu-devel] [PATCH] x86: Fix exceptions for fxsave/fxrstor Kevin Wolf
2009-10-04 10:05 ` Aurelien Jarno
2009-10-04 20:43 ` Kevin Wolf [this message]
2009-10-04 21:10 ` Aurelien Jarno
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=200910042243.54712@kevin-wolf.de \
--to=mail@kevin-wolf.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/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).