linux-kernel - Re: [PATCH v6 2/2] coresight: add coresight Trace Network On Chip driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <eb7dbabf-d878-468b-9945-36d8b14a4e65@quicinc.com>
Date: Tue, 3 Jun 2025 11:22:58 +0800
From: Yuanfang Zhang <quic_yuanfang@...cinc.com>
To: Leo Yan <leo.yan@....com>, Suzuki K Poulose <suzuki.poulose@....com>
CC: Mike Leach <mike.leach@...aro.org>, James Clark <james.clark@...aro.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Alexander Shishkin
	<alexander.shishkin@...ux.intel.com>,
        <kernel@....qualcomm.com>, <linux-arm-msm@...r.kernel.org>,
        <coresight@...ts.linaro.org>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 2/2] coresight: add coresight Trace Network On Chip
 driver



On 5/30/2025 8:59 PM, Leo Yan wrote:
> On Fri, May 30, 2025 at 12:32:23PM +0100, Suzuki Kuruppassery Poulose wrote:
> 
> [...]
> 
>>>> 2) How does the source driver know the TraceID for exposing via sysfs ?
>>>> Does it expose its own traceid ?
>>> No, sources connecting to TNOC don't have their own traceid, it expose the ATID which allocated in TNOC.
>>> TNOC will maintain the ID in coresight_path:: trace_id, when enable source, the source can get it from path.
>>>
>>> Here is the patch to expose id in source:
>>> https://patchwork.kernel.org/project/linux-arm-kernel/patch/20250530-showtraceid-v1-1-2761352cf7b4@quicinc.com/
>>
>> Please don't do that. We don't have to fake a traceid for all sources.
>> It is only of use to the decoder, with manual input from the user. So,
>> someone using the TNOC based system must be aware of how to collect the
>> traceid and as such expose it from the TNOC and not all the other
>> sources connected to it.
>>
>> Simply expose it on the TNOC device node
> 
> [...]
> 
>>>> Good question, since we have the "path" maintaining the TraceID, we
>>>> should use that here for the TNOC. But the other question is, can there be multiple sources connected to a single TNOC ? (I am guessing, yes!. And thus it may not work with what you are proposing.
>>>>
>>> yes, there can be multiple sources connected to one TNOC, and these sources share one Trace ID which allocate in TNOC.
>>> To decode the scenario relay on TraceID + Inport number, TraceID identifies the TNOC, the decoder maintains a table that maps each TNOC inport to its corresponding source.
> 
> If the Trace ID is only used to identify a TNOC, I am just wandering
> if can use self-contained method.
> 
> For example, you can generate a ID number based on the register base
> address, something like:
> 
>    /* TNOC physical address */
>    drvdata->paddr = res->start;
> 
>    if (IS_ENABLED(CONFIG_PHYS_ADDR_T_64BIT))
>        drvdata->atid = (drvdata->paddr >> 32) ^ (drvdata->paddr & 0xffffffffUL);
>    else
>        drvdata->atid = drvdata->paddr;
> 
> Then, you can get a unique ID for each TNOC in the system, and the
> ID is determined by the pyshical address and can be calculated
> directly by decoder.
> 
> Leo

Using both dynamic and self-contained IDs within the same system can result in ID conflicts, which may cause decoding failures.