All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH for-4.9] x86/vmx: Shorten vmx_{get, set}_segment_register() for user segments
Date: Thu, 17 Nov 2016 11:59:38 +0000	[thread overview]
Message-ID: <4ab1681f-27d4-ee82-8ed6-9f27518f7c1d@citrix.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D18E01F00A@SHSMSX101.ccr.corp.intel.com>

On 17/11/16 05:10, Tian, Kevin wrote:
>> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
>> Sent: Wednesday, November 16, 2016 9:42 PM
>>
>> On 26/10/16 14:15, Andrew Cooper wrote:
>>> The x86_segment enumeration matches hardware SReg encoding, which can be used
>>> to calculate the appropriate VMCS fields, rather than open coding every
>>> instance.
>>>
>>> This reduces the size of the switch statement, and the number of embedded BUG
>>> frames from the __vm{read,write}() calls.  In the unlikely case that a call
>>> does fault, the field can unambiguously be retrieved from the GPR state
>>> printed.
>>>
>>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>> ---
>>> CC: Jan Beulich <JBeulich@suse.com>
>>> CC: Jun Nakajima <jun.nakajima@intel.com>
>>> CC: Kevin Tian <kevin.tian@intel.com>
>> Intel: Ping?
> Acked-by: Kevin Tian <kevin.tian@intel.com>

Thanks.  Queued for 4.9.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-17 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 13:15 [PATCH for-4.9] x86/vmx: Shorten vmx_{get, set}_segment_register() for user segments Andrew Cooper
2016-10-26 13:40 ` Jan Beulich
2016-11-16 13:42 ` Andrew Cooper
2016-11-17  5:10   ` Tian, Kevin
2016-11-17 11:59     ` Andrew Cooper [this message]

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=4ab1681f-27d4-ee82-8ed6-9f27518f7c1d@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xen.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.