From: "Tian, Kevin" <kevin.tian@intel.com>
To: "Huang, Kai" <kai.huang@linux.intel.com>,
Jan Beulich <JBeulich@suse.com>,
"kaih.linux@gmail.com" <kaih.linux@gmail.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen: x86: remove duplicated IA32_FEATURE_CONTROL MSR macro
Date: Tue, 28 Jun 2016 02:27:02 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D15F8DB7B4@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <eddff572-b16a-a720-d857-0d48a17b4be8@linux.intel.com>
> From: Huang, Kai [mailto:kai.huang@linux.intel.com]
> Sent: Saturday, June 25, 2016 6:16 AM
> >
> >>> #define IA32_FEATURE_CONTROL_MSR_LOCK 0x0001
> >>> #define IA32_FEATURE_CONTROL_MSR_ENABLE_VMXON_INSIDE_SMX 0x0002
> >>> #define IA32_FEATURE_CONTROL_MSR_ENABLE_VMXON_OUTSIDE_SMX 0x0004
> >>> #define IA32_FEATURE_CONTROL_MSR_SENTER_PARAM_CTL 0x7f00
> >>> #define IA32_FEATURE_CONTROL_MSR_ENABLE_SENTER 0x8000
> >>> +#define IA32_FEATURE_CONTROL_MSR_SGX_ENABLE 0x40000
> >>
> >> suppose above macros better be changed in same style? Or is it
> >> really meaningful to keep whole MSR name in every bit definition?
> >> Is it clearly enough to just keep strings after _MSR_?
> >
> > I partly agree. The _MSR_ infix is clearly pointless. I wouldn't,
> > however, like to see the IA32_FEATURE_CONTROL_ prefix
> > dropped, as it helps associating the bits with their MSR.
>
> Sure. I think we can have consensus on just removing the _MSR_ infix, so
> the bit macros will be like IA32_FEATURE_CONTROL_LOCK,
> IA32_FEATURE_CONTROL_SGX_ENABLE, etc?
>
yes, sounds good to me.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-06-28 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 10:45 [PATCH] xen: x86: remove duplicated IA32_FEATURE_CONTROL MSR macro kaih.linux
2016-06-24 10:56 ` Tian, Kevin
2016-06-24 11:31 ` Jan Beulich
2016-06-24 22:16 ` Huang, Kai
2016-06-28 2:27 ` Tian, Kevin [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=AADFC41AFE54684AB9EE6CBC0274A5D15F8DB7B4@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=kai.huang@linux.intel.com \
--cc=kaih.linux@gmail.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.