From: Xiaoyao Li <xiaoyao.li@intel.com>
To: dongli.zhang@oracle.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: pbonzini@redhat.com, zhao1.liu@intel.com, mtosatti@redhat.com,
sandipan.das@amd.com, babu.moger@amd.com, likexu@tencent.com,
like.xu.linux@gmail.com, zhenyuw@linux.intel.com, groug@kaod.org,
khorenko@virtuozzo.com, alexander.ivanov@virtuozzo.com,
den@virtuozzo.com, davydov-max@yandex-team.ru,
dapeng1.mi@linux.intel.com, joe.jin@oracle.com
Subject: Re: [PATCH v2 01/10] target/i386: disable PerfMonV2 when PERFCORE unavailable
Date: Wed, 5 Mar 2025 09:38:19 +0800 [thread overview]
Message-ID: <1412c575-0a04-4d36-8b7f-e722da4d291f@intel.com> (raw)
In-Reply-To: <d6644767-3ed9-41be-847f-950d3666e0c6@oracle.com>
On 3/5/2025 6:53 AM, dongli.zhang@oracle.com wrote:
> Hi Xiaoyao,
>
> On 3/4/25 6:40 AM, Xiaoyao Li wrote:
>> On 3/3/2025 6:00 AM, Dongli Zhang wrote:
>>> When the PERFCORE is disabled with "-cpu host,-perfctr-core", it is
>>> reflected in in guest dmesg.
>>>
>>> [ 0.285136] Performance Events: AMD PMU driver.
>>
>> I'm a little confused. wWhen no perfctr-core, AMD PMU driver can still be
>> probed? (forgive me if I ask a silly question)
>
> Intel use "cpuid -1 -l 0xa" to determine the support of PMU.
>
> However, AMD doesn't use CPUID to determine PMU support (except AMD PMU
> PerfMonV2).
>
> I have derived everything from Linux kernel function amd_pmu_init().
>
> As line 1521, the PMU isn't supported by old AMD CPUs.
>
> 1516 __init int amd_pmu_init(void)
> 1517 {
> 1518 int ret;
> 1519
> 1520 /* Performance-monitoring supported from K7 and later: */
> 1521 if (boot_cpu_data.x86 < 6)
> 1522 return -ENODEV;
> 1523
> 1524 x86_pmu = amd_pmu;
> 1525
> 1526 ret = amd_core_pmu_init();
>
>
> 1. Therefore, at least 4 PMCs are available (without 'perfctr-core').
>
> 2. With 'perfctr-core', there are 6 PMCs. (line 1410)
>
> 1404 static int __init amd_core_pmu_init(void)
> 1405 {
> 1406 union cpuid_0x80000022_ebx ebx;
> 1407 u64 even_ctr_mask = 0ULL;
> 1408 int i;
> 1409
> 1410 if (!boot_cpu_has(X86_FEATURE_PERFCTR_CORE))
> 1411 return 0;
> 1412
> 1413 /* Avoid calculating the value each time in the NMI handler */
> 1414 perf_nmi_window = msecs_to_jiffies(100);
> 1415
> 1416 /*
> 1417 * If core performance counter extensions exists, we must use
> 1418 * MSR_F15H_PERF_CTL/MSR_F15H_PERF_CTR msrs. See also
> 1419 * amd_pmu_addr_offset().
> 1420 */
> 1421 x86_pmu.eventsel = MSR_F15H_PERF_CTL;
> 1422 x86_pmu.perfctr = MSR_F15H_PERF_CTR;
> 1423 x86_pmu.cntr_mask64 = GENMASK_ULL(AMD64_NUM_COUNTERS_CORE
> - 1, 0);
>
>
> 3. With PerfMonV2, extra global registers are available, as well as PMCs.
> (line 1426)
>
> 1425 /* Check for Performance Monitoring v2 support */
> 1426 if (boot_cpu_has(X86_FEATURE_PERFMON_V2)) {
> 1427 ebx.full = cpuid_ebx(EXT_PERFMON_DEBUG_FEATURES);
> 1428
> 1429 /* Update PMU version for later usage */
> 1430 x86_pmu.version = 2;
> 1431
> 1432 /* Find the number of available Core PMCs */
> 1433 x86_pmu.cntr_mask64 =
> GENMASK_ULL(ebx.split.num_core_pmc - 1, 0);
> 1434
> 1435 amd_pmu_global_cntr_mask = x86_pmu.cntr_mask64;
> 1436
> 1437 /* Update PMC handling functions */
> 1438 x86_pmu.enable_all = amd_pmu_v2_enable_all;
> 1439 x86_pmu.disable_all = amd_pmu_v2_disable_all;
> 1440 x86_pmu.enable = amd_pmu_v2_enable_event;
> 1441 x86_pmu.handle_irq = amd_pmu_v2_handle_irq;
> 1442 static_call_update(amd_pmu_test_overflow,
> amd_pmu_test_overflow_status);
> 1443 }
>
>
> That's why legacy 4-PMC PMU is probed after we disable perfctr-core.
>
> - (boot_cpu_data.x86 < 6): No PMU.
> - Without perfctr-core: 4 PMCs
> - With perfctr-core: 6 PMCs
> - PerfMonV2: PMCs (currently 6) + global PMU registers
>
>
> May this resolve your concern in another thread that "This looks like a KVM
> bug."? This isn't a KVM bug. It is because AMD's lack of the configuration
> to disable PMU.
It helps a lot! Yes, it doesn't a KVM bug.
Thanks for your elaborated explanation!
> Thank you very much!
>
> Dongli Zhang
>
>>
>>> However, the guest CPUID indicates the PerfMonV2 is still available.
>>>
>>> CPU:
>>> Extended Performance Monitoring and Debugging (0x80000022):
>>> AMD performance monitoring V2 = true
>>> AMD LBR V2 = false
>>> AMD LBR stack & PMC freezing = false
>>> number of core perf ctrs = 0x6 (6)
>>> number of LBR stack entries = 0x0 (0)
>>> number of avail Northbridge perf ctrs = 0x0 (0)
>>> number of available UMC PMCs = 0x0 (0)
>>> active UMCs bitmask = 0x0
>>>
>>> Disable PerfMonV2 in CPUID when PERFCORE is disabled.
>>>
>>> Suggested-by: Zhao Liu <zhao1.liu@intel.com>
>>
>> Though I have above confusion of the description, the change itself looks
>> good to me. So
>>
>> Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
>>
>>> Fixes: 209b0ac12074 ("target/i386: Add PerfMonV2 feature bit")
>>> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
>>> ---
>>> Changed since v1:
>>> - Use feature_dependencies (suggested by Zhao Liu).
>>>
>>> target/i386/cpu.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
>>> index 72ab147e85..b6d6167910 100644
>>> --- a/target/i386/cpu.c
>>> +++ b/target/i386/cpu.c
>>> @@ -1805,6 +1805,10 @@ static FeatureDep feature_dependencies[] = {
>>> .from = { FEAT_7_1_EDX, CPUID_7_1_EDX_AVX10 },
>>> .to = { FEAT_24_0_EBX, ~0ull },
>>> },
>>> + {
>>> + .from = { FEAT_8000_0001_ECX, CPUID_EXT3_PERFCORE },
>>> + .to = { FEAT_8000_0022_EAX,
>>> CPUID_8000_0022_EAX_PERFMON_V2 },
>>> + },
>>> };
>>> typedef struct X86RegisterInfo32 {
>>
>
next prev parent reply other threads:[~2025-03-05 1:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 22:00 [PATCH v2 00/10] target/i386/kvm/pmu: PMU Enhancement, Bugfix and Cleanup Dongli Zhang
2025-03-02 22:00 ` [PATCH v2 01/10] target/i386: disable PerfMonV2 when PERFCORE unavailable Dongli Zhang
2025-03-04 14:40 ` Xiaoyao Li
2025-03-04 22:53 ` dongli.zhang
2025-03-05 1:38 ` Xiaoyao Li [this message]
2025-03-05 14:20 ` Zhao Liu
2025-03-07 7:24 ` Sandipan Das
2025-03-02 22:00 ` [PATCH v2 02/10] target/i386: disable PERFCORE when "-pmu" is configured Dongli Zhang
2025-03-03 1:59 ` Xiaoyao Li
2025-03-03 18:45 ` dongli.zhang
2025-03-04 6:11 ` Xiaoyao Li
2025-03-06 16:50 ` Zhao Liu
2025-03-06 17:47 ` dongli.zhang
2025-03-07 7:41 ` Zhao Liu
2025-03-02 22:00 ` [PATCH v2 03/10] [DO NOT MERGE] kvm: Introduce kvm_arch_pre_create_vcpu() Dongli Zhang
2025-03-05 14:46 ` Zhao Liu
2025-03-05 21:53 ` dongli.zhang
2025-03-07 7:52 ` Zhao Liu
2025-03-07 8:40 ` Xiaoyao Li
2025-03-02 22:00 ` [PATCH v2 04/10] target/i386/kvm: set KVM_PMU_CAP_DISABLE if "-pmu" is configured Dongli Zhang
2025-03-04 7:59 ` Xiaoyao Li
2025-03-05 1:22 ` Sean Christopherson
2025-03-05 1:35 ` Xiaoyao Li
2025-03-05 14:41 ` Zhao Liu
2025-03-05 20:13 ` dongli.zhang
2025-03-05 14:44 ` Zhao Liu
2025-03-02 22:00 ` [PATCH v2 05/10] target/i386/kvm: extract unrelated code out of kvm_x86_build_cpuid() Dongli Zhang
2025-03-05 7:03 ` Mi, Dapeng
2025-03-07 9:15 ` Zhao Liu
2025-03-07 22:47 ` Dongli Zhang
2025-03-10 3:55 ` Zhao Liu
2025-03-02 22:00 ` [PATCH v2 06/10] target/i386/kvm: rename architectural PMU variables Dongli Zhang
2025-03-05 7:07 ` Mi, Dapeng
2025-03-07 9:19 ` Zhao Liu
2025-03-07 22:49 ` Dongli Zhang
2025-03-02 22:00 ` [PATCH v2 07/10] target/i386/kvm: query kvm.enable_pmu parameter Dongli Zhang
2025-03-10 6:14 ` Zhao Liu
2025-03-10 15:41 ` Dongli Zhang
2025-03-10 16:49 ` Dongli Zhang
2025-03-02 22:00 ` [PATCH v2 08/10] target/i386/kvm: reset AMD PMU registers during VM reset Dongli Zhang
2025-03-05 7:33 ` Mi, Dapeng
2025-03-05 11:41 ` Francesco Lavra
2025-03-05 19:05 ` dongli.zhang
2025-03-07 7:38 ` Sandipan Das
2025-03-10 7:47 ` Zhao Liu
2025-03-10 16:39 ` Dongli Zhang
2025-03-11 13:51 ` Zhao Liu
2025-03-11 19:52 ` Dongli Zhang
2025-03-12 8:30 ` Zhao Liu
2025-03-12 22:17 ` Dongli Zhang
2025-03-28 6:29 ` ewanhai
2025-03-28 16:42 ` Dongli Zhang
2025-03-31 3:55 ` ewanhai
2025-03-31 19:16 ` Dongli Zhang
2025-04-01 3:35 ` Ewan Hai
2025-04-07 8:51 ` Zhao Liu
2025-04-07 9:33 ` Ewan Hai
2025-04-16 8:17 ` Mi, Dapeng
2025-03-02 22:00 ` [PATCH v2 09/10] target/i386/kvm: support perfmon-v2 for reset Dongli Zhang
2025-03-02 22:00 ` [PATCH v2 10/10] target/i386/kvm: don't stop Intel PMU counters Dongli Zhang
2025-03-05 7:35 ` Mi, Dapeng
2025-03-05 19:00 ` dongli.zhang
2025-03-06 1:38 ` Mi, Dapeng
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=1412c575-0a04-4d36-8b7f-e722da4d291f@intel.com \
--to=xiaoyao.li@intel.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=babu.moger@amd.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=davydov-max@yandex-team.ru \
--cc=den@virtuozzo.com \
--cc=dongli.zhang@oracle.com \
--cc=groug@kaod.org \
--cc=joe.jin@oracle.com \
--cc=khorenko@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=likexu@tencent.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sandipan.das@amd.com \
--cc=zhao1.liu@intel.com \
--cc=zhenyuw@linux.intel.com \
/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).