From: George Dunlap <george.dunlap@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Kevin Tian <kevin.tian@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 2/2] x86/vmx: Drop ept_get_*() helpers
Date: Mon, 30 Jan 2017 18:01:50 +0000 [thread overview]
Message-ID: <cfd1496f-af58-4e92-4c4c-d4e750abd1d1@citrix.com> (raw)
In-Reply-To: <1485795243-15484-2-git-send-email-andrew.cooper3@citrix.com>
On 30/01/17 16:54, Andrew Cooper wrote:
> The ept_get_*() helpers are not used consistently, and are more verbose than
> the code they wrap. Drop the wrappers and use the internal union names
> consistently.
>
> While making these adjustments, drop the redundant ept_* prefix from mt, wl
> and ad, and rename the asr field to mfn for consistency with Xen's existing
> terminology.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-30 18:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:54 [PATCH 1/2] x86/vmx: Introduce a bitfield structure for EPT_VIOLATION EXIT_QUALIFICATIONs Andrew Cooper
2017-01-30 16:54 ` [PATCH 2/2] x86/vmx: Drop ept_get_*() helpers Andrew Cooper
2017-01-30 18:01 ` George Dunlap [this message]
2017-01-31 10:22 ` Jan Beulich
2017-02-08 7:06 ` Tian, Kevin
2017-01-31 10:19 ` [PATCH 1/2] x86/vmx: Introduce a bitfield structure for EPT_VIOLATION EXIT_QUALIFICATIONs Jan Beulich
2017-01-31 10:39 ` Andrew Cooper
2017-01-31 10:56 ` Jan Beulich
2017-02-08 7:06 ` Tian, Kevin
2017-02-08 10:42 ` [PATCH v2 " Andrew Cooper
2017-02-08 10:44 ` Andrew Cooper
2017-02-08 11:53 ` Jan Beulich
2017-02-08 11:56 ` Andrew Cooper
2017-02-08 12:30 ` Jan Beulich
2017-02-08 13:03 ` Andrew Cooper
2017-02-08 13:28 ` Jan Beulich
2017-02-08 15:04 ` Andrew Cooper
2017-02-08 15:46 ` Jan Beulich
2017-02-09 0:41 ` Tian, Kevin
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=cfd1496f-af58-4e92-4c4c-d4e750abd1d1@citrix.com \
--to=george.dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.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 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).