From: James Clark <james.clark@linaro.org>
To: Jie Gan <quic_jiegan@quicinc.com>
Cc: Tingwei Zhang <quic_tingweiz@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Subject: Re: [PATCH v10 4/7] Coresight: Introduce a new struct coresight_path
Date: Fri, 14 Feb 2025 11:09:16 +0000 [thread overview]
Message-ID: <b61af324-7488-4a4f-9f9e-2ecb004fc4c7@linaro.org> (raw)
In-Reply-To: <4b521b49-7104-4f25-82cb-4f9be7b235f4@quicinc.com>
On 14/02/2025 1:34 am, Jie Gan wrote:
>
>
> On 2/14/2025 12:00 AM, James Clark wrote:
>>
>>
>> On 07/02/2025 6:42 am, Jie Gan wrote:
>>> Add 'struct coresight_path' to store the data that is needed by
>>> coresight_enable_path/coresight_disable_path. The structure will be
>>> transmitted to any required devices to enable related funcationalities.
>>>
>>> The trace_id will be allocated after the path is built. Consequently,
>>> The ETM3x and ETM4x devices will directly read the trace_id from path
>>> which result in etm_read_alloc_trace_id and etm4_read_alloc_trace_id
>>> being deleted.
>>>
>>> Co-developed-by: James Clark <james.clark@linaro.org>
>>> Signed-off-by: James Clark <james.clark@linaro.org>
>>> Signed-off-by: Jie Gan <quic_jiegan@quicinc.com>
>>> ---
>>> drivers/hwtracing/coresight/coresight-core.c | 106 +++++++++++++-----
>>> drivers/hwtracing/coresight/coresight-dummy.c | 5 +-
>>> .../hwtracing/coresight/coresight-etm-perf.c | 30 +++--
>>> .../hwtracing/coresight/coresight-etm-perf.h | 2 +-
>>> drivers/hwtracing/coresight/coresight-etm.h | 1 -
>>> .../coresight/coresight-etm3x-core.c | 54 ++-------
>>> .../coresight/coresight-etm4x-core.c | 54 ++-------
>>> drivers/hwtracing/coresight/coresight-etm4x.h | 1 -
>>> drivers/hwtracing/coresight/coresight-priv.h | 12 +-
>>> drivers/hwtracing/coresight/coresight-stm.c | 3 +-
>>> drivers/hwtracing/coresight/coresight-sysfs.c | 17 ++-
>>> drivers/hwtracing/coresight/coresight-tpdm.c | 3 +-
>>> include/linux/coresight.h | 12 +-
>>> 13 files changed, 143 insertions(+), 157 deletions(-)
>>>
>> [...]
>>> @@ -352,7 +352,7 @@ static void *etm_setup_aux(struct perf_event
>>> *event, void **pages,
>>> * CPUs, we can handle it and fail the session.
>>> */
>>> for_each_cpu(cpu, mask) {
>>> - struct list_head *path;
>>> + struct coresight_path *path;
>>> struct coresight_device *csdev;
>>> csdev = per_cpu(csdev_src, cpu);
>>> @@ -405,15 +405,15 @@ static void *etm_setup_aux(struct perf_event
>>> *event, void **pages,
>>> cpumask_clear_cpu(cpu, mask);
>>> continue;
>>> }
>>> -
>>> /* ensure we can allocate a trace ID for this CPU */
>>> - trace_id = coresight_trace_id_get_cpu_id_map(cpu, &sink-
>>> >perf_sink_id_map);
>>> - if (!IS_VALID_CS_TRACE_ID(trace_id)) {
>>> + trace_id = coresight_path_assign_trace_id(path, CS_MODE_PERF);
>>> +
>>> + /* Can be 0 and valid, ETE doesn't need an ID */
>>> + if (trace_id < 0) {
>>
>> Not sure why I wrote it like this, but I think we should leave it as
>> it was with !IS_VALID_CS_TRACE_ID(). Even with ETE it calls the trace
>> ID allocator, so nothing has changed here.
>>
> Sure, Will restore. For ETE or ETM, we dont need traverse the path, just
> directly allocate the trace id based on cpu id.
>
> Jie
>
>
Sorry I meant to only keep the !IS_VALID_CS_TRACE_ID() bit. We still
need to call the new coresight_path_assign_trace_id() otherwise it
doesn't get assigned to the path. I saw that got removed in v11.
next prev parent reply other threads:[~2025-02-14 11:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 6:42 [PATCH v10 0/7] Coresight: Add Coresight TMC Control Unit driver Jie Gan
2025-02-07 6:42 ` [PATCH v10 1/7] Coresight: Add support for new APB clock name Jie Gan
2025-02-07 6:42 ` [PATCH v10 2/7] Coresight: Add trace_id function to retrieving the trace ID Jie Gan
2025-02-07 6:42 ` [PATCH v10 3/7] Coresight: Use coresight_etm_get_trace_id() in traceid_show() Jie Gan
2025-02-07 6:42 ` [PATCH v10 4/7] Coresight: Introduce a new struct coresight_path Jie Gan
2025-02-08 5:48 ` kernel test robot
2025-02-13 16:00 ` James Clark
2025-02-14 1:34 ` Jie Gan
2025-02-14 11:09 ` James Clark [this message]
2025-02-17 1:14 ` Jie Gan
2025-02-17 9:23 ` James Clark
2025-02-07 6:42 ` [PATCH v10 5/7] dt-bindings: arm: Add Coresight TMC Control Unit hardware Jie Gan
2025-02-07 6:42 ` [PATCH v10 6/7] Coresight: Add Coresight TMC Control Unit driver Jie Gan
2025-02-07 6:42 ` [PATCH v10 7/7] arm64: dts: qcom: sa8775p: Add CTCU and ETR nodes Jie Gan
2025-02-13 16:01 ` [PATCH v10 0/7] Coresight: Add Coresight TMC Control Unit driver James Clark
2025-02-14 1:36 ` Jie Gan
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=b61af324-7488-4a4f-9f9e-2ecb004fc4c7@linaro.org \
--to=james.clark@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=quic_jiegan@quicinc.com \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=robh@kernel.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