From: Leo Yan <leo.yan@arm.com>
To: "Johnny.Fan" <johnny.fan@cixtech.com>
Cc: will@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org, suzuki.poulose@arm.com,
mike.leach@arm.com, james.clark@linaro.org, maz@kernel.org,
jeremy.linton@arm.com, cix-kernel-upstream@cixtech.com,
bob.zhang@cixtech.com, jie.fu@cixtech.com,
Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v2] perf: arm_spe: Support heterogeneous ACPI systems
Date: Fri, 23 Oct 2026 17:19:54 +0100 [thread overview]
Message-ID: <20261023161954.GL26205@e132581.arm.com> (raw)
In-Reply-To: <20261021020322.3015121-1-johnny.fan@cixtech.com>
On Wed, Oct 21, 2026 at 10:03:22AM +0800, Johnny.Fan wrote:
> These synthetic devices have no fwnode, so the firmware-described
> IRQ affinity cannot tell which CPUs implement the feature. Pass the
> CPU mask as platform data and have the drivers prefer it over the
> IRQ affinity when present.
Could the MADT-derived CPU masks be exposed through
platform_get_irq_affinity(), so SPE and TRBE can continue using the
common interface without fetching ACPI-specific data?
TBC, I don't know ACPI or GIC. I just thought it might be a neat
approach.
> Apply the same treatment to TRBE, which shares this registration
> code. TRBE must also pass a stable copy of the mask to
> request_percpu_irq_affinity(), since supported_cpus is pruned as
> CPUs are probed.
I wouldn't expect any changes to the SPE or TRBE drivers if
platform_get_irq_affinity() can return the correct CPU mask.
Thanks,
Leo
prev parent reply other threads:[~2026-10-23 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 2:03 [PATCH v2] perf: arm_spe: Support heterogeneous ACPI systems Johnny.Fan
2026-10-23 16:19 ` Leo Yan [this message]
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=20261023161954.GL26205@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=bob.zhang@cixtech.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=coresight@lists.linaro.org \
--cc=fugang.duan@cixtech.com \
--cc=james.clark@linaro.org \
--cc=jeremy.linton@arm.com \
--cc=jie.fu@cixtech.com \
--cc=johnny.fan@cixtech.com \
--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=mike.leach@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