From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/6] x86emul: simplify FPU destination operand handling
Date: Wed, 7 Dec 2016 14:54:03 +0000 [thread overview]
Message-ID: <ef371c93-2eac-512c-db8c-6399ecf852f6@citrix.com> (raw)
In-Reply-To: <5846D5610200007800125C1F@prv-mh.provo.novell.com>
On 06/12/16 14:12, Jan Beulich wrote:
> Consolidate the copying of ea to dst: There's no need to set the type
> to OP_MEM, and instead the load cases setting it to OP_NONE allows the
> copying to be done just once per major opcode.
>
> 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-07 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 14:04 [PATCH 0/6] x86emul: FPU handling improvements Jan Beulich
2016-12-06 14:11 ` [PATCH 1/6] x86emul: extend / amend supported FPU opcodes Jan Beulich
2016-12-07 14:35 ` Andrew Cooper
2016-12-07 15:00 ` Jan Beulich
2016-12-06 14:12 ` [PATCH 2/6] x86emul: simplify FPU source operand handling Jan Beulich
2016-12-07 14:50 ` Andrew Cooper
2016-12-06 14:12 ` [PATCH 3/6] x86emul: simplify FPU destination " Jan Beulich
2016-12-07 14:54 ` Andrew Cooper [this message]
2016-12-06 14:13 ` [PATCH 4/6] x86emul: reduce FPU handling code size Jan Beulich
2016-12-07 15:06 ` Andrew Cooper
2016-12-07 15:16 ` Jan Beulich
2016-12-07 15:21 ` Andrew Cooper
2016-12-06 14:13 ` [PATCH 5/6] x86emul: avoid undefined behavior when dealing with 10-byte FPU operands Jan Beulich
2016-12-07 15:12 ` Andrew Cooper
2016-12-06 14:14 ` [PATCH 6/6] x86emul: simplify FPU handling asm() constraints Jan Beulich
2016-12-07 15:16 ` Andrew Cooper
2016-12-07 15:36 ` Jan Beulich
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=ef371c93-2eac-512c-db8c-6399ecf852f6@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).