All of lore.kernel.org
 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 3/3] x86emul: some REX related polishing
Date: Tue, 20 Dec 2016 11:29:51 +0000	[thread overview]
Message-ID: <44428803-7622-c84f-06eb-13787a7cdb74@citrix.com> (raw)
In-Reply-To: <584E83600200007800127DD7@prv-mh.provo.novell.com>

On 12/12/2016 10:00, Jan Beulich wrote:
> While there are a few cases where it seems better to open-code REX_*
> values, there's one where this clearly is a bad idea. And the SYSEXIT
> emulation has no need to look at REX at all, it can simply use op_bytes
> instead.
>
> 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:[~2016-12-20 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  9:38 [PATCH 0/3] x86emul: misc adjustments Jan Beulich
2016-12-12  9:59 ` [PATCH 1/3] x86emul: correct EFLAGS.TF handling Jan Beulich
2016-12-12 10:00 ` [PATCH 2/3 v2] x86emul: conditionally clear BNDn for branches Jan Beulich
2017-01-04 21:11   ` Andrew Cooper
2017-01-05  9:13     ` Jan Beulich
2017-01-05 18:59       ` Andrew Cooper
2017-01-06 15:35         ` Jan Beulich
2017-01-06 17:16           ` Jan Beulich
2016-12-12 10:00 ` [PATCH 3/3] x86emul: some REX related polishing Jan Beulich
2016-12-20 11:29   ` Andrew Cooper [this message]
2016-12-20  9:04 ` Ping: [PATCH 0/3] x86emul: misc adjustments Jan Beulich
2016-12-20 11:30   ` Andrew Cooper
2016-12-20 11:56     ` 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=44428803-7622-c84f-06eb-13787a7cdb74@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 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.