xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v5 02/17] x86emul: support MMX/SSE{, 2, 3} moves
Date: Tue, 7 Mar 2017 14:05:01 +0000	[thread overview]
Message-ID: <2006d265-6fdb-f8c9-70e9-3ddfc5d17b67@citrix.com> (raw)
In-Reply-To: <58B99299020000780013FE3D@prv-mh.provo.novell.com>

On 03/03/17 14:58, Jan Beulich wrote:
> Previously supported insns are being converted to the new model, and
> several new ones are being added.
>
> To keep the stub handling reasonably simple, integrate SET_SSE_PREFIX()
> into copy_REX_VEX(), at once switching the stubs to use an empty REX
> prefix instead of a double DS: one (no byte registers are being
> accessed, so an empty REX prefix has no effect), except (of course) for
> the 32-bit test harness build.
>
> 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

  reply	other threads:[~2017-03-07 14:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 14:47 [PATCH v5 00/17] x86emul: MMX/SSEn support Jan Beulich
2017-03-03 14:56 ` [PATCH v5 01/17] " Jan Beulich
2017-03-07 11:15   ` Andrew Cooper
2017-03-03 14:58 ` [PATCH v5 01/17] x86emul: support most memory accessing MMX/SSE{, 2, 3} insns Jan Beulich
2017-03-07 10:27   ` Jan Beulich
2017-03-03 14:58 ` [PATCH v5 02/17] x86emul: support MMX/SSE{,2,3} moves Jan Beulich
2017-03-07 14:05   ` Andrew Cooper [this message]
2017-03-03 14:59 ` [PATCH v5 03/17] x86emul: support MMX/SSE/SSE2 converts Jan Beulich
2017-03-03 14:59 ` [PATCH v5 04/17] x86emul: support {,V}{,U}COMIS{S,D} Jan Beulich
2017-03-07 14:13   ` [PATCH v5 04/17] x86emul: support {, V}{, U}COMIS{S, D} Andrew Cooper
2017-03-03 15:00 ` [PATCH v5 05/17] x86emul: support MMX/SSE{, 2, 4a} insns with only register operands Jan Beulich
2017-03-03 15:00 ` [PATCH v5 06/17] x86emul: support {,V}{LD,ST}MXCSR Jan Beulich
2017-03-03 15:01 ` [PATCH v5 07/17] x86emul: support {,V}MOVNTDQA Jan Beulich
2017-03-03 15:02 ` [PATCH v5 08/17] x86emul: test coverage for SSE/SSE2 insns Jan Beulich
2017-03-03 15:02 ` [PATCH v5 09/17] x86emul: honor MMXEXT feature flag Jan Beulich
2017-03-03 15:03 ` [PATCH v5 10/17] x86emul: add tables for 0f38 and 0f3a extension space Jan Beulich
2017-03-07 14:18   ` Andrew Cooper
2017-03-03 15:04 ` [PATCH v5 11/17] x86emul: support SSSE3 insns Jan Beulich
2017-03-03 15:04 ` [PATCH v5 12/17] x86emul: support SSE4.1 insns Jan Beulich
2017-03-07 14:24   ` Andrew Cooper
2017-03-03 15:05 ` [PATCH v5 13/17] x86emul: support SSE4.2 insns Jan Beulich
2017-03-03 15:06 ` [PATCH v5 14/17] x86emul: test coverage for SSE3/SSSE3/SSE4* insns Jan Beulich
2017-03-03 15:07 ` [PATCH v5 15/17] x86emul: support PCLMULQDQ Jan Beulich
2017-03-07 14:28   ` Andrew Cooper
2017-03-03 15:07 ` [PATCH v5 016/17] x86emul: support AESNI insns Jan Beulich
2017-03-07 14:32   ` Andrew Cooper
2017-03-03 15:08 ` [PATCH v5 17/17] x86emul: support SHA insns 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=2006d265-6fdb-f8c9-70e9-3ddfc5d17b67@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).