From: James Clark <james.clark@linaro.org>
To: scclevenger@os.amperecomputing.com, coresight@lists.linaro.org
Cc: yeoreum.yun@arm.com, Mike Leach <mike.leach@linaro.org>,
Jonathan Corbet <corbet@lwn.net>, Leo Yan <leo.yan@linux.dev>,
Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coresight: docs: Remove target sink from examples
Date: Tue, 17 Dec 2024 17:17:01 +0000 [thread overview]
Message-ID: <50e4aab7-d262-48a0-b956-2c2df0faeb25@linaro.org> (raw)
In-Reply-To: <75ce4def-b0ca-428f-99a5-19ca98e876a0@os.amperecomputing.com>
On 12/12/2024 7:38 pm, Steve Clevenger wrote:
>
>
> On 12/12/2024 7:27 AM, James Clark wrote:
>>
>>
>> On 11/12/2024 6:01 pm, Steve Clevenger wrote:
>>>
>>> Hi James,
>>>
>>> I thought I'd mention this issue with multicore self-hosted trace. The
>>> perf command line syntax does not allow a sink "type" to be specified
>>> (e.g. @tmc_etf or @tmc_etr). For multicore, it doesn't make sense to
>>> specify a processor mapped sink as would be the case for single core
>>> trace. A sink "type" should be allowed to avoid the auto select default.
>>> In our case, the default is the ETF sink.
>>>
>>> Thanks,
>>> Steve C.
>>>
>>
>> I'm sure it would be possible to add support for this, but I'm wondering
>> if the real issue is that the default selection logic is wrong? Are you
>> saying the default you get is ETF but you want ETR? And there is both
>> for each ETM? The default selection logic isn't easy to summarize but it
>> should prefer ETR (sysmem) over ETF (link sink), see coresight_find_sink().
>>
>> It's probably better to fix that rather than add a new sink selection
>> feature. Maybe if you shared a diagram of your coresight architecture it
>> would help.
>>
>> Thanks
>> James
>
> Hi James,
>
> It appears the default sink selection is ETF for multicore trace. In any
> case, for the Arm® CoreSight Base System Architecture STC Level
> compliance, I need to be able to specify the sink type.
Yep it makes sense to add support for selecting it then then, I will put
it on the list but not sure about the priority. I think looking into why
the default isn't working is more important for now.
>
> The Ampere CoreSight hierarchy is described to the ACPI as follows:
>
>
> +-----------------+
> | |
> | ETM |
> | |
> +--------+--------+
> |
> |
> +--------+--------+
> | |
> | ETF |
> | |
> +--------+--------+
> |
> |
> +--------+--------+
> | |
> | ETR |
> | |
> +--------+--------+
> |
> |
> +--------+--------+
> | |
> | CATU |
> | |
> +--------+--------+
>
> Steve C.
>
I recreated this in the test here:
https://lore.kernel.org/linux-kernel/20241217171132.834943-1-james.clark@linaro.org/T/#u
But it looks like it correctly selects ETR rather than ETF, so I'm not
sure what the difference is between your setup and that. If you can have
a look at that test and compare it that would be very helpful.
Thanks
James
next prev parent reply other threads:[~2024-12-17 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 14:49 [PATCH] coresight: docs: Remove target sink from examples James Clark
2024-12-11 18:01 ` Steve Clevenger
2024-12-12 15:27 ` James Clark
2024-12-12 19:38 ` Steve Clevenger
2024-12-17 17:17 ` James Clark [this message]
2025-03-05 15:51 ` James Clark
2025-03-11 10:22 ` Leo Yan
2025-03-11 10:51 ` James Clark
2025-03-11 13:57 ` Leo Yan
2025-03-11 14:57 ` Suzuki K Poulose
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=50e4aab7-d262-48a0-b956-2c2df0faeb25@linaro.org \
--to=james.clark@linaro.org \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=scclevenger@os.amperecomputing.com \
--cc=yeoreum.yun@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;
as well as URLs for NNTP newsgroup(s).