From: Yuanfang Zhang <quic_yuanfang@quicinc.com>
To: Leo Yan <leo.yan@arm.com>
Cc: <suzuki.poulose@arm.com>, <mike.leach@linaro.org>,
<james.clark@linaro.org>, <alexander.shishkin@linux.intel.com>,
<coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] coresight-etm4x: add isb() before reading the TRCSTATR
Date: Fri, 13 Dec 2024 17:18:14 +0800 [thread overview]
Message-ID: <1e99294f-b528-4cf7-a0e0-3d78221e6982@quicinc.com> (raw)
In-Reply-To: <20241204151650.GA1976757@e132581.arm.com>
On 12/4/2024 11:16 PM, Leo Yan wrote:
> Hi Yuanfang,
>
> Recently I just acrossed this part, so some comments.
>
> On Wed, Dec 04, 2024 at 07:23:32PM +0800, yuanfang zhang wrote:
>>
>> From: Yuanfang Zhang <quic_yuanfang@quicinc.com>
>>
>> As recommended by section 4.3.7 ("Synchronization when using system
>> instructions to progrom the trace unit") of ARM IHI 0064H.b, the
>> self-hosted trace analyzer must perform a Context synchronization
>> event between writing to the TRCPRGCTLR and reading the TRCSTATR.
>>
>> Fixes: ebddaad09e10 ("coresight: etm4x: Add missing single-shot control API to sysfs")
>> Signed-off-by: Yuanfang Zhang <quic_yuanfang@quicinc.com>
>> ---
>> Change in V2:
>> Added comments in the code.
>> drivers/hwtracing/coresight/coresight-etm4x-core.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-etm4x-core.c b/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> index 66d44a404ad0..decb3a87e27e 100644
>> --- a/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> +++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> @@ -906,6 +906,13 @@ static void etm4_disable_hw(void *info)
>> tsb_csync();
>> etm4x_relaxed_write32(csa, control, TRCPRGCTLR);
>>
>> + /*
>> + * As recommended by section 4.3.7 ("Synchronization when using system
>> + * instructions to progrom the trace unit") of ARM IHI 0064H.b, the
>> + * self-hosted trace analyzer must perform a Context synchronization
>> + * event between writing to the TRCPRGCTLR and reading the TRCSTATR.
>> + */
>> + isb();
>
> As described in the doc, the "isb" is only required for system
> instructions case. It is good to only apply the ISB on system
> register case:
>
> if (!csa->io_mem)
> isb();
>
updated in PATCH V3.
>> /* wait for TRCSTATR.PMSTABLE to go to '1' */
>> if (coresight_timeout(csa, TRCSTATR, TRCSTATR_PMSTABLE_BIT, 1))
>> dev_err(etm_dev,
>
> As mentioned in system register case: "Arm recommends that the
> self-hosted trace analyzer always executes an ISB instruction after
> programming the trace unit registers, to ensure that all updates are
> committed to the trace unit before normal code execution resumes."
>
> And for MMIO case:
>
> "When the memory is marked as Device-nGnRE or stronger.
> ...
> - Poll TRCSTATR to ensure the previous write has completed.
> — Execute an ISB operation."
>
> Thus we need to add an ISB after polling.
>
> isb();
>
updated in PATCH V3.
> For consistent behaviour, a relevant thing is the dsb(sy) in
> etm4_enable_hw(). I do not think the dsb(sy) is necessary, as the
> driver uses the sequence "write TRCPRGCTLR + polling TRCSTATR" to
> ensure the data has been populated to trace unit, the polling
> operations somehow act as a read back. And the ETM manual does not
> mention the requirement for DSB when enabling trace unit. Thus, we
> should remove dsb(sy) (maybe use a separte patch).
>
updated in PATCH V3.
> Mike / Suzuki / James, please confirm if my conclusions are valid.
>
> Thanks,
> Leo
prev parent reply other threads:[~2024-12-13 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:23 yuanfang zhang
2024-12-04 15:16 ` Leo Yan
2024-12-13 9:18 ` Yuanfang Zhang [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=1e99294f-b528-4cf7-a0e0-3d78221e6982@quicinc.com \
--to=quic_yuanfang@quicinc.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--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
all inboxes | Powered by JetHome®