mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johnny Fan <johnny.fan@cixtech.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Marc Zyngier <maz@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	will@kernel.org, mark.rutland@arm.com, james.clark@linaro.org,
	leo.yan@arm.com, cix-kernel-upstream@cixtech.com,
	bob.zhang@cixtech.com, jie.fu@cixtech.com,
	fugang.duan@cixtech.com
Subject: Re: [PATCH] perf: arm_spe: Support heterogeneous ACPI systems
Date: Fri, 16 Oct 2026 12:20:13 +0800	[thread overview]
Message-ID: <atGl/ZTg49t/VfVj@JohnnyFan> (raw)
In-Reply-To: <14d16970-915b-4c86-afeb-bfc3058564df@arm.com>

On Thu, Oct 15, 2026 at 10:58:10AM -0500, Jeremy Linton wrote:
> I don't think the GICC is sufficient, you have to consider actual
> heterogeneous machines that have differing SPE implementations with the
> same PMSVer, which mean you have to keep the PPTT hetid check, and set
> the mask based on both it and the GSIV. Then, like DT create multiple
> platform devices. Which is true with the current patch as well, the
> hetid still needs to be there even if you have differing PPI's because
> it could have more than two differing implementations.

Following that direction, the question on ACPI is how each registered
SPE device gets its supported_cpus: the platform devices are created
without an fwnode, so platform_get_irq_affinity() falls back to
cpu_possible_mask today, regardless of which CPUs actually implement
SPE. That's the plumbing question I asked Marc about -- would be good
to know if you have a preference here too.

Thanks,

Johnny
> 

  reply	other threads:[~2026-10-16  4:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  6:29 Johnny.Fan
2026-10-15 10:49 ` Marc Zyngier
2026-10-15 11:52   ` Johnny Fan
2026-10-15 15:58     ` Jeremy Linton
2026-10-16  4:20       ` Johnny Fan [this message]
2026-10-15 14:19   ` Leo Yan
2026-10-16  3:24     ` Johnny Fan

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=atGl/ZTg49t/VfVj@JohnnyFan \
    --to=johnny.fan@cixtech.com \
    --cc=bob.zhang@cixtech.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=fugang.duan@cixtech.com \
    --cc=james.clark@linaro.org \
    --cc=jeremy.linton@arm.com \
    --cc=jie.fu@cixtech.com \
    --cc=leo.yan@arm.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=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®