From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Madhavan Srinivasan <maddy@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Subject: Re: [PATCH kernel] powerpc/perf: Stop crashing with generic_compat_pmu
Date: Wed, 2 Dec 2020 14:01:55 +1100 [thread overview]
Message-ID: <848255d6-5c8f-d4c2-a865-e3a7ffce7fdb@ozlabs.ru> (raw)
In-Reply-To: <c3852667-210c-48de-7f89-a06250b4df05@linux.ibm.com>
Hi Maddy,
I just noticed that I still have "powerpc/perf: Add checks for reserved
values" in my pile (pushed here
https://github.com/aik/linux/commit/61e1bc3f2e19d450e2e2d39174d422160b21957b
), do we still need it? The lockups I saw were fixed by
https://github.com/aik/linux/commit/17899eaf88d689 but it is hardly a
replacement. Thanks,
On 04/06/2020 02:34, Madhavan Srinivasan wrote:
>
>
> On 6/2/20 8:26 AM, Alexey Kardashevskiy wrote:
>> The bhrb_filter_map ("The Branch History Rolling Buffer") callback is
>> only defined in raw CPUs' power_pmu structs. The "architected" CPUs use
>> generic_compat_pmu which does not have this callback and crashed occur.
>>
>> This add a NULL pointer check for bhrb_filter_map() which behaves as if
>> the callback returned an error.
>>
>> This does not add the same check for config_bhrb() as the only caller
>> checks for cpuhw->bhrb_users which remains zero if bhrb_filter_map==0.
>
> Changes looks fine.
> Reviewed-by: Madhavan Srinivasan <maddy@linux.ibm.com>
>
> The commit be80e758d0c2e ('powerpc/perf: Add generic compat mode pmu
> driver')
> which introduced generic_compat_pmu was merged in v5.2. So we need to
> CC stable starting from 5.2 :( . My bad, sorry.
>
> Maddy
>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>> arch/powerpc/perf/core-book3s.c | 19 ++++++++++++++-----
>> 1 file changed, 14 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/powerpc/perf/core-book3s.c
>> b/arch/powerpc/perf/core-book3s.c
>> index 3dcfecf858f3..36870569bf9c 100644
>> --- a/arch/powerpc/perf/core-book3s.c
>> +++ b/arch/powerpc/perf/core-book3s.c
>> @@ -1515,9 +1515,16 @@ static int power_pmu_add(struct perf_event
>> *event, int ef_flags)
>> ret = 0;
>> out:
>> if (has_branch_stack(event)) {
>> - power_pmu_bhrb_enable(event);
>> - cpuhw->bhrb_filter = ppmu->bhrb_filter_map(
>> - event->attr.branch_sample_type);
>> + u64 bhrb_filter = -1;
>> +
>> + if (ppmu->bhrb_filter_map)
>> + bhrb_filter = ppmu->bhrb_filter_map(
>> + event->attr.branch_sample_type);
>> +
>> + if (bhrb_filter != -1) {
>> + cpuhw->bhrb_filter = bhrb_filter;
>> + power_pmu_bhrb_enable(event); /* Does bhrb_users++ */
>> + }
>> }
>>
>> perf_pmu_enable(event->pmu);
>> @@ -1839,7 +1846,6 @@ static int power_pmu_event_init(struct
>> perf_event *event)
>> int n;
>> int err;
>> struct cpu_hw_events *cpuhw;
>> - u64 bhrb_filter;
>>
>> if (!ppmu)
>> return -ENOENT;
>> @@ -1945,7 +1951,10 @@ static int power_pmu_event_init(struct
>> perf_event *event)
>> err = power_check_constraints(cpuhw, events, cflags, n + 1);
>>
>> if (has_branch_stack(event)) {
>> - bhrb_filter = ppmu->bhrb_filter_map(
>> + u64 bhrb_filter = -1;
>> +
>> + if (ppmu->bhrb_filter_map)
>> + bhrb_filter = ppmu->bhrb_filter_map(
>> event->attr.branch_sample_type);
>>
>> if (bhrb_filter == -1) {
>
--
Alexey
next prev parent reply other threads:[~2020-12-02 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 2:56 [PATCH kernel] powerpc/perf: Stop crashing with generic_compat_pmu Alexey Kardashevskiy
2020-06-03 16:34 ` Madhavan Srinivasan
2020-12-02 3:01 ` Alexey Kardashevskiy [this message]
2020-12-03 5:27 ` Madhavan Srinivasan
2021-02-16 1:06 ` Alexey Kardashevskiy
2020-08-27 7:46 ` Michael Ellerman
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=848255d6-5c8f-d4c2-a865-e3a7ffce7fdb@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=maddy@linux.vnet.ibm.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).