From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, Leo Yan <leo.yan@linux.dev>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/7] perf cs-etm: Don't hard code config attribute when configuring the event
Date: Tue, 2 Dec 2025 12:15:28 +0000 [thread overview]
Message-ID: <20251202121528.GX724103@e132581.arm.com> (raw)
In-Reply-To: <20251201-james-perf-config-bits-v1-6-22ecbbf8007c@linaro.org>
On Mon, Dec 01, 2025 at 04:41:09PM +0000, Coresight ML wrote:
[...]
> @@ -103,13 +103,20 @@ static int cs_etm_validate_context_id(struct perf_pmu *cs_etm_pmu, struct evsel
> struct perf_cpu cpu)
> {
> int err;
> - __u64 val;
> - u64 contextid = evsel->core.attr.config &
> - (perf_pmu__format_bits(cs_etm_pmu, "contextid") |
> - perf_pmu__format_bits(cs_etm_pmu, "contextid1") |
> - perf_pmu__format_bits(cs_etm_pmu, "contextid2"));
> + u64 ctxt, ctxt1, ctxt2;
> + __u64 trcidr2;
>
> - if (!contextid)
> + err = evsel__get_config_val(cs_etm_pmu, evsel, "contextid", &ctxt);
> + if (err)
> + return err;
> + err = evsel__get_config_val(cs_etm_pmu, evsel, "contextid1", &ctxt1);
> + if (err)
> + return err;
> + err = evsel__get_config_val(cs_etm_pmu, evsel, "contextid2", &ctxt2);
> + if (err)
> + return err;
Seems to me, this is not right. The current code checks any context
ID setting but it can tolerate if missing "contexid[*]" format.
After calling evsel__get_config_val(), if any "contextid[*]" format is
missed, it returns error and will diretly bail out. As a result,
cs_etm_validate_context_id() will always return error.
> +
> + if (!ctxt && !ctxt1 && !ctxt2)
> return 0;
>
> /* Not supported in etmv3 */
> @@ -120,12 +127,11 @@ static int cs_etm_validate_context_id(struct perf_pmu *cs_etm_pmu, struct evsel
> }
>
> /* Get a handle on TRCIDR2 */
> - err = cs_etm_get_ro(cs_etm_pmu, cpu, metadata_etmv4_ro[CS_ETMV4_TRCIDR2], &val);
> + err = cs_etm_get_ro(cs_etm_pmu, cpu, metadata_etmv4_ro[CS_ETMV4_TRCIDR2], &trcidr2);
> if (err)
> return err;
>
> - if (contextid &
> - perf_pmu__format_bits(cs_etm_pmu, "contextid1")) {
> + if (ctxt1) {
> /*
> * TRCIDR2.CIDSIZE, bit [9-5], indicates whether contextID
> * tracing is supported:
> @@ -133,15 +139,14 @@ static int cs_etm_validate_context_id(struct perf_pmu *cs_etm_pmu, struct evsel
> * 0b00100 Maximum of 32-bit Context ID size.
> * All other values are reserved.
> */
> - if (BMVAL(val, 5, 9) != 0x4) {
> + if (BMVAL(trcidr2, 5, 9) != 0x4) {
> pr_err("%s: CONTEXTIDR_EL1 isn't supported, disable with %s/contextid1=0/\n",
> CORESIGHT_ETM_PMU_NAME, CORESIGHT_ETM_PMU_NAME);
> return -EINVAL;
> }
> }
>
> - if (contextid &
> - perf_pmu__format_bits(cs_etm_pmu, "contextid2")) {
> + if (ctxt2) {
> /*
> * TRCIDR2.VMIDOPT[30:29] != 0 and
> * TRCIDR2.VMIDSIZE[14:10] == 0b00100 (32bit virtual contextid)
> @@ -149,7 +154,7 @@ static int cs_etm_validate_context_id(struct perf_pmu *cs_etm_pmu, struct evsel
> * virtual context id is < 32bit.
> * Any value of VMIDSIZE >= 4 (i.e, > 32bit) is fine for us.
> */
> - if (!BMVAL(val, 29, 30) || BMVAL(val, 10, 14) < 4) {
> + if (!BMVAL(trcidr2, 29, 30) || BMVAL(trcidr2, 10, 14) < 4) {
> pr_err("%s: CONTEXTIDR_EL2 isn't supported, disable with %s/contextid2=0/\n",
> CORESIGHT_ETM_PMU_NAME, CORESIGHT_ETM_PMU_NAME);
> return -EINVAL;
> @@ -163,10 +168,14 @@ static int cs_etm_validate_timestamp(struct perf_pmu *cs_etm_pmu, struct evsel *
> struct perf_cpu cpu)
> {
> int err;
> - __u64 val;
> + u64 val;
> + __u64 trcidr0;
>
> - if (!(evsel->core.attr.config &
> - perf_pmu__format_bits(cs_etm_pmu, "timestamp")))
> + err = evsel__get_config_val(cs_etm_pmu, evsel, "timestamp", &val);
> + if (err)
> + return err;
> +
> + if (!val)
> return 0;
Similiar issue here. The current code returns 0 if not find "timestamp"
format. With this change, it returns error instead.
Thanks,
Leo
next prev parent reply other threads:[~2025-12-02 12:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 16:41 [PATCH 0/7] perf cs-etm/arm-spe: Remove hard coded config fields James Clark
2025-12-01 16:41 ` [PATCH 1/7] perf tools: Track all user changed config bits James Clark
2025-12-02 10:15 ` Leo Yan
2025-12-02 10:40 ` James Clark
2025-12-02 11:21 ` Leo Yan
2025-12-02 12:36 ` Leo Yan
2025-12-01 16:41 ` [PATCH 2/7] perf tools: apply evsel__set_config_if_unset() to all config fields James Clark
2025-12-02 11:14 ` Leo Yan
2025-12-04 10:55 ` James Clark
2025-12-01 16:41 ` [PATCH 3/7] perf cs-etm: Make a helper to find the Coresight evsel James Clark
2025-12-02 11:24 ` Leo Yan
2025-12-01 16:41 ` [PATCH 4/7] perf cs-etm: Don't use hard coded config bits when setting up ETMCR James Clark
2025-12-02 11:43 ` Leo Yan
2025-12-02 11:53 ` James Clark
2025-12-04 10:55 ` James Clark
2025-12-04 13:45 ` Mike Leach
2025-12-04 13:48 ` James Clark
2025-12-01 16:41 ` [PATCH 5/7] perf cs-etm: Don't use hard coded config bits when setting up TRCCONFIGR James Clark
2025-12-02 12:01 ` Leo Yan
2025-12-01 16:41 ` [PATCH 6/7] perf cs-etm: Don't hard code config attribute when configuring the event James Clark
2025-12-02 12:15 ` Leo Yan [this message]
2025-12-04 14:08 ` James Clark
2025-12-04 14:43 ` Leo Yan
2025-12-01 16:41 ` [PATCH 7/7] perf arm-spe: Don't hard code config attribute James Clark
2025-12-02 12:28 ` Leo Yan
2025-12-02 12:42 ` Leo Yan
2025-12-02 12:59 ` 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=20251202121528.GX724103@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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).