From: Leo Yan <leo.yan@arm.com>
To: Igor Velkov <iav@iav.lv>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@arm.com>,
James Clark <james.clark@linaro.org>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: coresight: cpu-debug: PC sampling via PMPCSR (FEAT_PCSRv8p2)?
Date: Thu, 19 Nov 2026 15:17:21 +0000 [thread overview]
Message-ID: <20261119151721.GZ9176@e132581.arm.com> (raw)
In-Reply-To: <20261118-coresight-pmpcsr-reply-leo-3@iav.lv>
On Wed, Nov 18, 2026 at 08:58:26PM +0200, Igor Velkov wrote:
> On Wed, Nov 18, 2026 at 10:49:17AM +0000, Leo Yan wrote:
> > 1) If idle_cpu(cpu) == 0, sample the CPU directly.
> > 2) If idle_cpu(cpu) == 1, follow the existing flow to request
> > power-up before sampling.
>
> I tried step 2 on RK3399 (Cortex-A53 + A72, cpuidle with core
> powerdown), following debug_read_regs() on a running system:
>
> - Idle A53 (EDPRSR.PU = 0): the EDOSLAR write raises an SError on the
> reading CPU. COREPURQ brings the core up only for a moment; with
> COREPURQ | CORENPDRQ it is off again within 10 ms, and the write
> still faults.
> - Idle A72 (PU = 1, R = 1): the same SError on the EDOSLAR write.
> - Busy CPUs (idle_cpu() == 0) on both clusters: no errors, full PC.
>
> So on this SoC only step 1 is safe.
This is why I suggested 3) in my previous reply. Seems you should skip
sample idle CPUs if COREPURQ/CORENPDRQ are not properly integrated in
the SoC.
Thanks,
Leo
prev parent reply other threads:[~2026-11-19 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 5:46 coresight: cpu-debug: PC sampling via PMPCSR (FEAT_PCSRv8p2)? Igor Velkov
2026-11-13 9:25 ` Suzuki K Poulose
2026-11-13 14:46 ` Leo Yan
2026-11-14 0:08 ` Igor Velkov
2026-11-17 18:32 ` Leo Yan
2026-11-17 18:50 ` Igor Velkov
2026-11-18 10:49 ` Leo Yan
2026-11-18 18:58 ` Igor Velkov
2026-11-19 15:17 ` 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=20261119151721.GZ9176@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=coresight@lists.linaro.org \
--cc=iav@iav.lv \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mike.leach@arm.com \
--cc=suzuki.poulose@arm.com \
/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