From: Sandipan Das <sandipan.das@amd.com>
To: Like Xu <like.xu.linux@gmail.com>, peterz@infradead.org
Cc: bp@alien8.de, dave.hansen@linux.intel.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, jolsa@kernel.org, tglx@linutronix.de,
mingo@redhat.com, pbonzini@redhat.com, jmattson@google.com,
eranian@google.com, puwen@hygon.cn, ananth.narayan@amd.com,
ravi.bangoria@amd.com, santosh.shukla@amd.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v4 5/7] perf/x86/amd/core: Add PerfMonV2 counter control
Date: Mon, 9 May 2022 15:28:07 +0530 [thread overview]
Message-ID: <0b9dced9-a080-1b00-3315-5ba22537558f@amd.com> (raw)
In-Reply-To: <c313e9c9-97eb-8273-5bb7-553692e8e2f5@gmail.com>
On 5/9/2022 12:35 PM, Like Xu wrote:
> On 27/4/2022 7:31 pm, Sandipan Das wrote:
>
>> static void amd_pmu_add_event(struct perf_event *event)
>> {
>> if (needs_branch_stack(event))
>> @@ -1216,6 +1251,11 @@ static int __init amd_core_pmu_init(void)
>> x86_pmu.num_counters = ebx.split.num_core_pmc;
>> amd_pmu_global_cntr_mask = (1ULL << x86_pmu.num_counters) - 1;
>> +
>> + /* Update PMC handling functions */
>> + x86_pmu.enable_all = amd_pmu_v2_enable_all;
>> + x86_pmu.disable_all = amd_pmu_v2_disable_all;
>> + x86_pmu.enable = amd_pmu_v2_enable_event;
>> }
>
> Considering the below part of code also run on the PerfMonV2 host
>
> whatever the guest PMU version, how about updating these two use cases as well in this patch ?
>
> diff --git a/arch/x86/events/amd/core.c b/arch/x86/events/amd/core.c
> index 262e39a85031..2f7c62e46314 100644
> --- a/arch/x86/events/amd/core.c
> +++ b/arch/x86/events/amd/core.c
> @@ -1469,8 +1469,8 @@ void amd_pmu_enable_virt(void)
> cpuc->perf_ctr_virt_mask = 0;
>
> /* Reload all events */
> - amd_pmu_disable_all();
> - x86_pmu_enable_all(0);
> + amd_pmu.disable_all();
> + amd_pmu.enable_all(0);
> }
> EXPORT_SYMBOL_GPL(amd_pmu_enable_virt);
>
> @@ -1487,7 +1487,7 @@ void amd_pmu_disable_virt(void)
> cpuc->perf_ctr_virt_mask = AMD64_EVENTSEL_HOSTONLY;
>
> /* Reload all events */
> - amd_pmu_disable_all();
> - x86_pmu_enable_all(0);
> + amd_pmu.disable_all();
> + amd_pmu.enable_all(0);
> }
> EXPORT_SYMBOL_GPL(amd_pmu_disable_virt);
>
Good point. I had made these changes as a part of the guest PerfMonV2
enablement.
Peter,
Since these patches are now in perf/core, should I send out a separate
fix for this?
- Sandipan
next prev parent reply other threads:[~2022-05-09 9:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 11:31 [PATCH v4 0/7] perf/x86/amd/core: Add AMD PerfMonV2 support Sandipan Das
2022-04-27 11:31 ` [PATCH v4 1/7] x86/cpufeatures: Add PerfMonV2 feature bit Sandipan Das
2022-04-27 11:31 ` [PATCH v4 2/7] x86/msr: Add PerfCntrGlobal* registers Sandipan Das
2022-04-27 11:31 ` [PATCH v4 3/7] perf/x86/amd/core: Detect PerfMonV2 support Sandipan Das
2022-05-09 13:01 ` Like Xu
2022-05-09 13:08 ` Sandipan Das
2022-05-09 13:11 ` Peter Zijlstra
2022-05-10 8:36 ` Sandipan Das
2022-04-27 11:31 ` [PATCH v4 4/7] perf/x86/amd/core: Detect available counters Sandipan Das
2022-04-27 11:31 ` [PATCH v4 5/7] perf/x86/amd/core: Add PerfMonV2 counter control Sandipan Das
2022-05-09 7:05 ` Like Xu
2022-05-09 9:58 ` Sandipan Das [this message]
2022-05-09 11:24 ` Peter Zijlstra
2022-04-27 11:31 ` [PATCH v4 6/7] perf/x86/amd/core: Add PerfMonV2 overflow handling Sandipan Das
2022-04-28 13:40 ` Like Xu
2022-04-29 5:10 ` Sandipan Das
2022-04-27 11:31 ` [PATCH v4 7/7] kvm: x86/cpuid: Fix CPUID leaf 0xA Sandipan Das
2022-05-02 23:50 ` Jim Mattson
2022-05-03 12:01 ` Paolo Bonzini
2022-05-03 12:04 ` Paolo Bonzini
2022-04-27 11:37 ` [PATCH v4 0/7] perf/x86/amd/core: Add AMD PerfMonV2 support Borislav Petkov
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=0b9dced9-a080-1b00-3315-5ba22537558f@amd.com \
--to=sandipan.das@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=jmattson@google.com \
--cc=jolsa@kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=ravi.bangoria@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome