From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, Brendan Gregg <bgregg@netflix.com>
Cc: andrew.cooper3@citrix.com, kevin.tian@intel.com,
dietmar.hahn@ts.fujitsu.com, jun.nakajima@intel.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v5] x86/VPMU: implement ipc and arch filter flags
Date: Wed, 6 Jan 2016 09:16:47 -0500 [thread overview]
Message-ID: <568D21CF.3070104@oracle.com> (raw)
In-Reply-To: <568D0BDA02000078000C3E32@prv-mh.provo.novell.com>
On 01/06/2016 06:43 AM, Jan Beulich wrote:
>>>> On 05.01.16 at 02:43, <bgregg@netflix.com> wrote:
>> This introduces a way to have a restricted VPMU, by specifying one of two
>> predefined groups of PMCs to make available. For secure environments, this
>> allows the VPMU to be used without needing to enable all PMCs.
>>
>> Signed-off-by: Brendan Gregg <bgregg@netflix.com>
>> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Does this hold with ...
>
>> ---
>> Changes in v5:
>> * addressing review comments from Kevin:
>> * simplified BTS DS_AREA filter
>> * improvements to comments, incl. matching Intel SDM descriptions
> ... all of these?
>
Yes.
Note that this patch will conflict with
http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg02753.html (for
'case MSR_IA32_PEBS_ENABLE' in core2_vpmu_do_wrmsr()). I can rebase it
on top of Brendan's if you prefer.
-boris
next prev parent reply other threads:[~2016-01-06 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 1:43 [PATCH v5] x86/VPMU: implement ipc and arch filter flags Brendan Gregg
2016-01-05 6:52 ` Tian, Kevin
2016-01-06 11:43 ` Jan Beulich
2016-01-06 14:16 ` Boris Ostrovsky [this message]
2016-01-07 14:12 ` Jan Beulich
2016-01-07 21:40 ` Brendan Gregg
2016-01-08 7:52 ` 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=568D21CF.3070104@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=bgregg@netflix.com \
--cc=dietmar.hahn@ts.fujitsu.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.