From: James Clark <james.clark@linaro.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 04/13] coresight: Hide unused ETMv3 format attributes
Date: Tue, 18 Nov 2025 14:56:33 +0000 [thread overview]
Message-ID: <0334300a-ae81-4b55-a3b0-c6137e13be6a@linaro.org> (raw)
In-Reply-To: <20251114145521.GD3568724@e132581.arm.com>
On 14/11/2025 2:55 pm, Leo Yan wrote:
> On Wed, Nov 12, 2025 at 03:22:10PM +0000, James Clark wrote:
>> ETMv3 only has a few attributes, and setting unused ones results in an
>> error, so hide them to begin with.
>>
>> Signed-off-by: James Clark <james.clark@linaro.org>
>> ---
>> drivers/hwtracing/coresight/coresight-etm-perf.c | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-etm-perf.c b/drivers/hwtracing/coresight/coresight-etm-perf.c
>> index 17afa0f4cdee..91132abca244 100644
>> --- a/drivers/hwtracing/coresight/coresight-etm-perf.c
>> +++ b/drivers/hwtracing/coresight/coresight-etm-perf.c
>> @@ -106,8 +106,27 @@ static struct attribute *etm_config_formats_attr[] = {
>> NULL,
>> };
>>
>> +static umode_t etm_format_attr_is_visible(struct kobject *kobj,
>> + struct attribute *attr, int unused)
>> +{
>> + /* ETM4 has all attributes */
>> + if (IS_ENABLED(CONFIG_CORESIGHT_SOURCE_ETM4X))
>> + return attr->mode;
>> +
>> + /* ETM3 only has these attributes */
>> + if (attr == &format_attr_cycacc.attr ||
>> + attr == &format_attr_timestamp.attr ||
>> + attr == &format_attr_retstack.attr ||
>> + attr == &format_attr_sinkid.attr ||
>> + attr == &format_attr_configid.attr)
>
> Do we support configid for ETM3?
>
They're "activated" in etm_setup_aux() so this would be for both ETM3
and 4. But they're only subsequently "enabled" for ETM4. So no, they're
not supported. I'll hide this attribute too.
I can leave it for a later fix if we want to stop activating them, but I
don't think it does any harm.
>> + return attr->mode;
>
> It is good to give a bit information why only these attributes
> supported, e.g.,
>
> /*
> * ETM3 only support subset attributes (see ETM3X_SUPPORTED_OPTIONS),
> * keep 'sinkid' attr for specifying sink ID.
> */
>
> Two side topics but not issues caused this patch:
>
> - Since CTXTID/CTXTID2 is only used for ETM4x, we can remove "#if
> IS_ENABLED(CONFIG_CORESIGHT_SOURCE_ETM4X)" from the
> format_attr_contextid_show() function.
Will change to CONFIG_ARM64 as mentioned on the other thread.
>
> - etm_parse_event_config() does not check attr->config3, thus user
> sets 'cc_threshold' it will slip without any error report.
Will ignore this comment as mentioned on patch 7, we're not doing any
errors for unsupported arguments anymore.
>
> Thanks,
> Leo
>
>> +
>> + return 0;
>> +}
>> +
>> static const struct attribute_group etm_pmu_format_group = {
>> .name = "format",
>> + .is_visible = etm_format_attr_is_visible,
>> .attrs = etm_config_formats_attr,
>> };
>>
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2025-11-18 14:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 15:22 [PATCH v4 00/13] coresight: Update timestamp attribute to be an interval instead of bool James Clark
2025-11-12 15:22 ` [PATCH v4 01/13] coresight: Change syncfreq to be a u8 James Clark
2025-11-14 12:20 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 02/13] coresight: Repack struct etmv4_drvdata James Clark
2025-11-12 15:22 ` [PATCH v4 03/13] coresight: Refactor etm4_config_timestamp_event() James Clark
2025-11-12 15:22 ` [PATCH v4 04/13] coresight: Hide unused ETMv3 format attributes James Clark
2025-11-14 14:55 ` Leo Yan
2025-11-18 14:56 ` James Clark [this message]
2025-11-12 15:22 ` [PATCH v4 05/13] coresight: Define format attributes with GEN_PMU_FORMAT_ATTR() James Clark
2025-11-14 15:03 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 06/13] coresight: Interpret ETMv3 config with ATTR_CFG_GET_FLD() James Clark
2025-11-14 15:07 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 07/13] coresight: Don't reject unrecognized ETMv3 format attributes James Clark
2025-11-14 15:18 ` Leo Yan
2025-11-14 15:21 ` James Clark
2025-11-12 15:22 ` [PATCH v4 08/13] coresight: Interpret perf config with ATTR_CFG_GET_FLD() James Clark
2025-11-14 15:30 ` Leo Yan
2025-11-14 15:34 ` James Clark
2025-11-14 15:41 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 09/13] coresight: Interpret ETMv4 " James Clark
2025-11-14 16:09 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 10/13] coresight: Remove misleading definitions James Clark
2025-11-14 16:23 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 11/13] coresight: Extend width of timestamp format attribute James Clark
2025-11-14 17:10 ` Leo Yan
2025-11-12 15:22 ` [PATCH v4 12/13] coresight: Allow setting the timestamp interval James Clark
2025-11-12 15:22 ` [PATCH v4 13/13] coresight: docs: Document etm4x timestamp interval option James Clark
2025-11-14 5:02 ` Randy Dunlap
2025-11-14 9:59 ` James Clark
2025-11-14 18:05 ` Leo Yan
2025-11-18 16:15 ` James Clark
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=0334300a-ae81-4b55-a3b0-c6137e13be6a@linaro.org \
--to=james.clark@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@arm.com \
--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=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