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 5/5] perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU
Date: Fri, 2 Jun 2023 00:13:36 -0700 (PDT) [thread overview]
Message-ID: <607a395b-b01f-33e1-c67d-d4bd4d92c3d@os.amperecomputing.com> (raw)
In-Reply-To: <e15f1773-e843-3bc3-f265-65524ea3385a@arm.com>
Hi Robin,
On Thu, 1 Jun 2023, Robin Murphy wrote:
> On 2023-06-01 04:01, Ilkka Koskinen wrote:
> [...]
>> +static bool ampere_cspmu_validate_event(struct arm_cspmu *cspmu,
>> + struct perf_event *new)
>> +{
>> + struct perf_event *curr;
>> + unsigned int idx;
>> + u32 threshold = 0, rank = 0, bank = 0;
>> +
>> + /* We compare the global filter settings to existing events */
>> + idx = find_first_bit(cspmu->hw_events.used_ctrs,
>> + cspmu->cycle_counter_logical_idx);
>> +
>> + /* This is the first event */
>> + if (idx == cspmu->cycle_counter_logical_idx)
>> + return true;
>> +
>> + curr = cspmu->hw_events.events[idx];
>> +
>> + if (get_filter_enable(new)) {
>> + threshold = get_threshold(new);
>> + rank = get_rank(new);
>> + bank = get_bank(new);
>> + }
>> +
>> + if (get_filter_enable(new) != get_filter_enable(curr) ||
>
> Is there any useful purpose in allowing the user to specify nonzero rank,
> bank or threshold values with filter_enable=0? Assuming not, then between
> this and ampere_cspmu_set_ev_filter() it appears that you don't need
> filter_enable at all.
Not really. I dropped filter_enable at one point but restored it later to
match the smmuv3 pmu driver. I totally agree, it's unnecessary and it's
better to remove it completely.
Cheers, Ilkka
>
> Thanks,
> Robin.
>
>> + get_threshold(curr) != threshold ||
>> + get_rank(curr) != rank ||
>> + get_bank(curr) != bank)
>> + return false;
>> +
>> + return true;
>> +}
>
next prev parent reply other threads:[~2023-06-02 7:13 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
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 [this message]
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=607a395b-b01f-33e1-c67d-d4bd4d92c3d@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;
as well as URLs for NNTP newsgroup(s).