All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>,
	Kevin Tian <kevin.tian@intel.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Eddie Dong <eddie.dong@intel.com>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	"tim@xen.org" <tim@xen.org>,
	Jun Nakajima <jun.nakajima@intel.com>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>
Subject: Re: [PATCH RFC V8 3/5] xen, libxc: Force-enable relevant MSR events
Date: Thu, 28 Aug 2014 11:26:37 +0300	[thread overview]
Message-ID: <53FEE7BD.8080604@bitdefender.com> (raw)
In-Reply-To: <53FF0387020000780002E8C7@mail.emea.novell.com>

On 08/28/2014 11:25 AM, Jan Beulich wrote:
>>>> On 28.08.14 at 09:40, <rcojocaru@bitdefender.com> wrote:
>> On 08/27/2014 11:25 PM, Tian, Kevin wrote:
>>>> From: Razvan Cojocaru [mailto:rcojocaru@bitdefender.com]
>>>> +const u32 vmx_msrs_exit_array[] = {
>>>> +    MSR_IA32_SYSENTER_EIP,
>>>> +    MSR_IA32_SYSENTER_ESP,
>>>> +    MSR_IA32_SYSENTER_CS,
>>>> +    MSR_IA32_MC0_CTL,
>>>> +    MSR_STAR,
>>>> +    MSR_LSTAR
>>>> +};
>>>> +
>>>> +const unsigned int vmx_msrs_exit_array_size =
>>>> +    ARRAY_SIZE(vmx_msrs_exit_array);
>>>> +
>>>
>>> prefer a name including 'force' purpose or at least have a comment
>>> to describe the intention, so its meaning is explained as early as possible.
>>
>> How would vmx_force_enabled_msrs_array (with a comment added) sound to
>> you and Jan?
> 
> vmx_introspection_force_enabled_msrs[]?

No problem, I'll rename it to that.


Thanks,
Razvan Cojocaru

  reply	other threads:[~2014-08-28  8:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 14:01 [PATCH RFC V8 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-08-27 14:01 ` [PATCH RFC V8 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-08-27 14:01 ` [PATCH RFC V8 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-08-27 15:44   ` Jan Beulich
2014-08-27 20:25   ` Tian, Kevin
2014-08-28  7:40     ` Razvan Cojocaru
2014-08-28  8:25       ` Jan Beulich
2014-08-28  8:26         ` Razvan Cojocaru [this message]
2014-08-28 21:27       ` Tian, Kevin
2014-08-27 14:01 ` [PATCH RFC V8 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-08-27 15:46   ` Jan Beulich
2014-08-27 16:04     ` Razvan Cojocaru
2014-08-27 20:59   ` Tian, Kevin
2014-08-28  7:54     ` Razvan Cojocaru
2014-08-28 21:22       ` Tian, Kevin
2014-08-27 14:01 ` [PATCH RFC V8 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-08-27 15:52   ` Jan Beulich
2014-08-27 21:06     ` Tian, Kevin
2014-08-28  7:30       ` Razvan Cojocaru
2014-08-27 15:40 ` [PATCH RFC V8 1/5] xen: Emulate with no writes Jan Beulich
2014-08-27 15:42   ` Razvan Cojocaru

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=53FEE7BD.8080604@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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.