From: Nick Chan <towinchenmi@gmail.com>
To: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, devicetree@vger.kernel.org,
asahi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/10] drivers/perf: apple_m1: Support per-implementation event tables
Date: Wed, 12 Feb 2025 09:46:38 +0800 [thread overview]
Message-ID: <23db2d80-cfc4-4c15-a4fe-11e677185344@gmail.com> (raw)
In-Reply-To: <20250212-apple-cpmu-v1-2-f8c7f2ac1743@gmail.com>
Nick Chan 於 2025/2/12 凌晨12:07 寫道:
> Use per-implementation event tables to allow supporting implementations
> with a different list of events and event affinities.
>
> Signed-off-by: Nick Chan <towinchenmi@gmail.com>
> ---
> drivers/perf/apple_m1_cpu_pmu.c | 65 +++++++++++++++++++++++++----------------
> 1 file changed, 40 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/perf/apple_m1_cpu_pmu.c b/drivers/perf/apple_m1_cpu_pmu.c
> index 06fd317529fcbab0f1485228efe8470be565407c..1bf7ce5c09846c699d66bdfcca129f418a9dad9e 100644
> --- a/drivers/perf/apple_m1_cpu_pmu.c
> +++ b/drivers/perf/apple_m1_cpu_pmu.c
[...]
> static void m1_pmu_reset(void *info)
> @@ -572,25 +588,16 @@ static int m1_pmu_set_event_filter(struct hw_perf_event *event,
> return 0;
> }
>
> -static int m1_pmu_init(struct arm_pmu *cpu_pmu, u32 flags)
> +static int apple_pmu_init_common(struct arm_pmu *cpu_pmu, u32 flags)
> {
> cpu_pmu->handle_irq = m1_pmu_handle_irq;
> cpu_pmu->enable = m1_pmu_enable_event;
> cpu_pmu->disable = m1_pmu_disable_event;
> cpu_pmu->read_counter = m1_pmu_read_counter;
> cpu_pmu->write_counter = m1_pmu_write_counter;
> - cpu_pmu->get_event_idx = m1_pmu_get_event_idx;
> cpu_pmu->clear_event_idx = m1_pmu_clear_event_idx;
> cpu_pmu->start = m1_pmu_start;
> cpu_pmu->stop = m1_pmu_stop;
> -
> - if (flags & ARMPMU_EVT_47BIT)
> - cpu_pmu->map_event = m1_pmu_map_event;
> - else if (flags & ARMPMU_EVT_63BIT)
> - cpu_pmu->map_event = m2_pmu_map_event;
> - else
> - return WARN_ON(-EINVAL);
> -
> cpu_pmu->reset = m1_pmu_reset;
> cpu_pmu->set_event_filter = m1_pmu_set_event_filter;
[...]
The flags parameter is no longer used, so I will send a v2 with the parameter dropped.
Nick Chan
next prev parent reply other threads:[~2025-02-12 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 16:07 [PATCH 00/10] drivers/perf: apple_m1: Add Apple A7-A11, T2 SoC support Nick Chan
2025-02-11 16:07 ` [PATCH 01/10] dt-bindings: arm: pmu: Add Apple A7-A11 SoC CPU PMU compatibles Nick Chan
2025-02-11 16:07 ` [PATCH 02/10] drivers/perf: apple_m1: Support per-implementation event tables Nick Chan
2025-02-12 1:46 ` Nick Chan [this message]
2025-02-11 16:07 ` [PATCH 03/10] drivers/perf: apple_m1: Support a per-implementation number of counters Nick Chan
2025-02-11 16:07 ` [PATCH 04/10] drivers/perf: apple_m1: Support configuring counters for 32-bit EL0 Nick Chan
2025-02-11 16:07 ` [PATCH 05/10] drivers/perf: apple_m1: Support per-implementation PMU start Nick Chan
2025-02-11 16:07 ` [PATCH 06/10] drivers/perf: apple_m1: Add Apple A7 support Nick Chan
2025-02-11 16:07 ` [PATCH 07/10] drivers/perf: apple_m1: Add Apple A8/A8X support Nick Chan
2025-02-11 16:07 ` [PATCH 08/10] drivers/perf: apple_m1: Add A9/A9X support Nick Chan
2025-02-11 16:07 ` [PATCH 09/10] drivers/perf: apple_m1: Add Apple A10/A10X/T2 Support Nick Chan
2025-02-11 16:07 ` [PATCH 10/10] drivers/perf: apple_m1: Add Apple A11 Support Nick Chan
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=23db2d80-cfc4-4c15-a4fe-11e677185344@gmail.com \
--to=towinchenmi@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--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).