From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 1/6] x86emul: extend / amend supported FPU opcodes
Date: Thu, 8 Dec 2016 11:42:11 +0000 [thread overview]
Message-ID: <676b69ee-87ed-ead3-32b6-b00984934b4d@citrix.com> (raw)
In-Reply-To: <584953920200007800126A95@prv-mh.provo.novell.com>
On 08/12/16 11:35, Jan Beulich wrote:
> First of all there are a number of secondary encodings both Intel and
> AMD support, but which aren't formally documented. See e.g.
> www.sandpile.org/x86/opc_fpu.htm for inofficial documentation.
>
> Next there are a few more no-ops - instructions which served a purpose
> only on 8087 or 287.
>
> Further switch from fail_if() to raising of #UD in a couple of places
> (as the decoding of FPU opcodes should now be complete except where
> explicitly marked as todo).
>
> Also adjust a few comments.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-08 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 11:26 [PATCH v2 0/6] x86emul: FPU handling improvements Jan Beulich
2016-12-08 11:35 ` [PATCH v2 1/6] x86emul: extend / amend supported FPU opcodes Jan Beulich
2016-12-08 11:42 ` Andrew Cooper [this message]
2016-12-08 11:36 ` [PATCH v2 2/6] x86emul: simplify FPU source operand handling Jan Beulich
2016-12-08 11:36 ` [PATCH v2 3/6] x86emul: simplify FPU destination " Jan Beulich
2016-12-08 11:37 ` [PATCH v2 4/6] x86emul: reduce FPU handling code size Jan Beulich
2016-12-08 11:38 ` [PATCH v2 5/6] x86emul: avoid undefined behavior when dealing with 10-byte FPU operands Jan Beulich
2016-12-08 11:38 ` [PATCH v2 6/6] x86emul: simplify FPU handling asm() constraints Jan Beulich
2016-12-15 9:52 ` Ping: " Jan Beulich
2016-12-15 11:36 ` Andrew Cooper
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=676b69ee-87ed-ead3-32b6-b00984934b4d@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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).