From: sashiko-bot@kernel.org
To: Johnny.Fan <johnny.fan@cixtech.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 1/2] perf: arm_pmu: Accept a per-device CPU mask from platform data
Date: Mon, 02 Nov 2026 09:02:14 +0000 [thread overview]
Message-ID: <sashiko-outbox-193150@kernel.org> (raw)
In-Reply-To: <20261102084153.3975282-2-johnny.fan@cixtech.com>
> From: "Johnny.Fan" <Johnny.Fan@cixtech.com>
>
> Synthetic platform devices created from ACPI data have no fwnode, so
> platform_get_irq_affinity() cannot tell which CPUs implement the
> feature and falls back to cpu_possible_mask.
>
> Add an optional CPU mask to the platform data and make both the SPE and
> the TRBE drivers prefer it over the firmware-described IRQ affinity.
> Device tree devices have no platform data and keep using the affinity.
>
> TRBE must also pass a stable copy of the mask to
> request_percpu_irq_affinity(), because supported_cpus is pruned as CPUs
> are probed, while the IRQ action keeps a pointer to the mask.
>
> This is a preparatory change: no ACPI device carries platform data yet,
> so behaviour is unchanged.
>
> Signed-off-by: Johnny.Fan <Johnny.Fan@cixtech.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102084153.3975282-1-johnny.fan@cixtech.com?part=1
next prev parent reply other threads:[~2026-11-02 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 8:41 [PATCH v3 0/2] perf: arm_spe: Support heterogeneous ACPI systems Johnny.Fan
2026-11-02 8:41 ` [PATCH v3 1/2] perf: arm_pmu: Accept a per-device CPU mask from platform data Johnny.Fan
2026-11-02 9:02 ` sashiko-bot [this message]
2026-11-02 8:41 ` [PATCH v3 2/2] perf: arm_pmu_acpi: Support heterogeneous ACPI systems Johnny.Fan
2026-11-02 8:52 ` sashiko-bot
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=sashiko-outbox-193150@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=johnny.fan@cixtech.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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