From: Ilkka Koskinen <ilkka@os.amperecomputing.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] perf: arm_cspmu: Support implementation specific event validation
Date: Fri, 2 Jun 2023 00:09:24 -0700 (PDT) [thread overview]
Message-ID: <30a649f3-f787-56f-38a0-9ce0ef87f4ca@os.amperecomputing.com> (raw)
In-Reply-To: <2a081ab9-f1f3-569e-72e8-1c743e8357a1@arm.com>
Hi Robin,
On Thu, 1 Jun 2023, Robin Murphy wrote:
> On 2023-06-01 04:01, Ilkka Koskinen wrote:
>> Some platforms may use e.g. different filtering mechanism and, thus,
>> may need different way to validate the events.
>>
>> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>> ---
>> drivers/perf/arm_cspmu/arm_cspmu.c | 4 ++++
>> drivers/perf/arm_cspmu/arm_cspmu.h | 2 ++
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/drivers/perf/arm_cspmu/arm_cspmu.c
>> b/drivers/perf/arm_cspmu/arm_cspmu.c
>> index b4c4ef81c719..a26f484e06b1 100644
>> --- a/drivers/perf/arm_cspmu/arm_cspmu.c
>> +++ b/drivers/perf/arm_cspmu/arm_cspmu.c
>> @@ -593,6 +593,10 @@ static int arm_cspmu_get_event_idx(struct
>> arm_cspmu_hw_events *hw_events,
>> if (idx >= cspmu->num_logical_ctrs)
>> return -EAGAIN;
>> + if (cspmu->impl.ops.validate_event &&
>> + !cspmu->impl.ops.validate_event(cspmu, event))
>> + return -EAGAIN;
>
> Seems like this should be -EINVAL, or maybe the callback should return int so
> it can make its own distinction (yes, I know the outer logic doesn't actually
> propagate it, but there's no reason that couldn't improve at some point as
> well).
Makes sense to me.
> Another thought is that once we get into imp-def conditions for whether an
> event is valid in itself, we presumably also need to consider imp-def
> conditions for whether a given pair of events are compatible to be grouped?
That's a good point. I'll take a look at it.
Cheers, Ilkka
>
> Thanks,
> Robin.
>
>> +
>> set_bit(idx, hw_events->used_ctrs);
>> return idx;
>> diff --git a/drivers/perf/arm_cspmu/arm_cspmu.h
>> b/drivers/perf/arm_cspmu/arm_cspmu.h
>> index 4a29b921f7e8..0e5c316c96f9 100644
>> --- a/drivers/perf/arm_cspmu/arm_cspmu.h
>> +++ b/drivers/perf/arm_cspmu/arm_cspmu.h
>> @@ -106,6 +106,8 @@ struct arm_cspmu_impl_ops {
>> void (*set_ev_filter)(struct arm_cspmu *cspmu,
>> struct hw_perf_event *hwc,
>> u32 filter);
>> + /* Implementation specific event validation */
>> + bool (*validate_event)(struct arm_cspmu *cspmu, struct perf_event
>> *new);
>> /* Hide/show unsupported events */
>> umode_t (*event_attr_is_visible)(struct kobject *kobj,
>> struct attribute *attr, int unused);
>
next prev parent reply other threads:[~2023-06-02 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 3:01 [PATCH v2 0/5] perf: ampere: Add support for Ampere SoC PMUs Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 1/5] perf: arm_cspmu: Support 32-bit accesses to 64-bit registers Ilkka Koskinen
2023-06-01 14:49 ` Robin Murphy
2023-06-02 6:47 ` Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 2/5] perf: arm_cspmu: Support shared interrupts Ilkka Koskinen
2023-06-01 14:54 ` Robin Murphy
2023-06-02 7:04 ` Ilkka Koskinen
2023-06-02 11:25 ` Robin Murphy
2023-06-01 3:01 ` [PATCH v2 3/5] perf: arm_cspmu: Support implementation specific filters Ilkka Koskinen
2023-06-01 3:01 ` [PATCH v2 4/5] perf: arm_cspmu: Support implementation specific event validation Ilkka Koskinen
2023-06-01 15:09 ` Robin Murphy
2023-06-02 7:09 ` Ilkka Koskinen [this message]
2023-06-01 3:01 ` [PATCH v2 5/5] perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU Ilkka Koskinen
2023-06-01 15:23 ` Robin Murphy
2023-06-02 7:13 ` Ilkka Koskinen
2023-06-02 11:51 ` Robin Murphy
2023-06-03 1:16 ` kernel test robot
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=30a649f3-f787-56f-38a0-9ce0ef87f4ca@os.amperecomputing.com \
--to=ilkka@os.amperecomputing.com \
--cc=bwicaksono@nvidia.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®