From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: <andrew.cooper3@citrix.com>, <roger.pau@citrix.com>, <wl@xen.org>,
<jun.nakajima@intel.com>, <kevin.tian@intel.com>,
<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v4 1/2] x86/vtx: add LBR_SELECT to the list of LBR MSRs
Date: Thu, 15 Apr 2021 00:13:08 +0100 [thread overview]
Message-ID: <45ab2093-f140-1b91-f683-dc0ca17159c5@citrix.com> (raw)
In-Reply-To: <871c259b-487e-4c67-e648-b1aefef55df3@suse.com>
On 14/04/2021 12:41, Jan Beulich wrote:
> On 14.04.2021 06:40, Igor Druzhinin wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -2915,14 +2915,16 @@ static const struct lbr_info {
>> }, nh_lbr[] = {
>> { MSR_IA32_LASTINTFROMIP, 1 },
>> { MSR_IA32_LASTINTTOIP, 1 },
>> - { MSR_C2_LASTBRANCH_TOS, 1 },
>> + { MSR_NHL_LBR_SELECT, 1 },
>> + { MSR_NHL_LASTBRANCH_TOS, 1 },
>> { MSR_P4_LASTBRANCH_0_FROM_LIP, NUM_MSR_P4_LASTBRANCH_FROM_TO },
>> { MSR_P4_LASTBRANCH_0_TO_LIP, NUM_MSR_P4_LASTBRANCH_FROM_TO },
>> { 0, 0 }
>> }, sk_lbr[] = {
>> { MSR_IA32_LASTINTFROMIP, 1 },
>> { MSR_IA32_LASTINTTOIP, 1 },
>> - { MSR_SKL_LASTBRANCH_TOS, 1 },
>> + { MSR_NHL_LBR_SELECT, 1 },
>> + { MSR_NHL_LASTBRANCH_TOS, 1 },
>> { MSR_SKL_LASTBRANCH_0_FROM_IP, NUM_MSR_SKL_LASTBRANCH },
>> { MSR_SKL_LASTBRANCH_0_TO_IP, NUM_MSR_SKL_LASTBRANCH },
>> { MSR_SKL_LASTBRANCH_0_INFO, NUM_MSR_SKL_LASTBRANCH },
>> @@ -2937,6 +2939,7 @@ static const struct lbr_info {
>> }, gm_lbr[] = {
>> { MSR_IA32_LASTINTFROMIP, 1 },
>> { MSR_IA32_LASTINTTOIP, 1 },
>> + { MSR_GM_LBR_SELECT, 1 },
>
> What about Xeon Phi, Silvermont, and Airmont?
Yes, you're right - forgot about those. Will need to shuffle arrays a
little.
>> --- a/xen/include/asm-x86/msr-index.h
>> +++ b/xen/include/asm-x86/msr-index.h
>> @@ -606,14 +606,18 @@
>> #define NUM_MSR_C2_LASTBRANCH_FROM_TO 4
>> #define NUM_MSR_ATOM_LASTBRANCH_FROM_TO 8
>>
>> +/* Nehalem (and newer) last-branch recording */
>> +#define MSR_NHL_LBR_SELECT 0x000001c8
>> +#define MSR_NHL_LASTBRANCH_TOS 0x000001c9
>> +
>> /* Skylake (and newer) last-branch recording */
>> -#define MSR_SKL_LASTBRANCH_TOS 0x000001c9
>> #define MSR_SKL_LASTBRANCH_0_FROM_IP 0x00000680
>> #define MSR_SKL_LASTBRANCH_0_TO_IP 0x000006c0
>> #define MSR_SKL_LASTBRANCH_0_INFO 0x00000dc0
>> #define NUM_MSR_SKL_LASTBRANCH 32
>>
>> /* Goldmont last-branch recording */
>> +#define MSR_GM_LBR_SELECT 0x000001c8
>> #define MSR_GM_LASTBRANCH_TOS 0x000001c9
>
> Wouldn't it make sense to also re-use the NHL constants, like you
> do for Skylake?
I didn't really see GM to be derived from NHL so decided to split those.
Looks cleaner to me that way otherwise might be a little confusing to
use NHL constants in GM definitions. Given the change above - I will
have to reshuffle those anyway in v5.
Igor
next prev parent reply other threads:[~2021-04-14 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 4:40 [PATCH v4 1/2] x86/vtx: add LBR_SELECT to the list of LBR MSRs Igor Druzhinin
2021-04-14 4:40 ` [PATCH v4 2/2] x86/intel: insert Ice Lake-SP and Ice Lake-D model numbers Igor Druzhinin
2021-04-14 12:24 ` Jan Beulich
2021-04-14 11:41 ` [PATCH v4 1/2] x86/vtx: add LBR_SELECT to the list of LBR MSRs Jan Beulich
2021-04-14 23:13 ` Igor Druzhinin [this message]
2021-04-15 9:01 ` 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=45ab2093-f140-1b91-f683-dc0ca17159c5@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=wl@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.