From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>,
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>,
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 7/7] perf arm-spe: Don't hard code config attribute
Date: Tue, 2 Dec 2025 12:42:40 +0000 [thread overview]
Message-ID: <20251202124240.GA724103@e132581.arm.com> (raw)
In-Reply-To: <20251202122835.GY724103@e132581.arm.com>
On Tue, Dec 02, 2025 at 12:28:35PM +0000, Coresight ML wrote:
> On Mon, Dec 01, 2025 at 04:41:10PM +0000, Coresight ML wrote:
> > Use the config attribute that's published by the driver instead of
> > hard coding "attr.config".
> >
> > Signed-off-by: James Clark <james.clark@linaro.org>
> > ---
> > tools/perf/arch/arm64/util/arm-spe.c | 15 ++++++++-------
> > 1 file changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/tools/perf/arch/arm64/util/arm-spe.c b/tools/perf/arch/arm64/util/arm-spe.c
> > index d5ec1408d0ae..6c3dc97fde30 100644
> > --- a/tools/perf/arch/arm64/util/arm-spe.c
> > +++ b/tools/perf/arch/arm64/util/arm-spe.c
> > @@ -256,7 +256,7 @@ static __u64 arm_spe_pmu__sample_period(const struct perf_pmu *arm_spe_pmu)
> >
> > static void arm_spe_setup_evsel(struct evsel *evsel, struct perf_cpu_map *cpus)
> > {
> > - u64 bit;
> > + u64 pa_enable_bit;
> >
> > evsel->core.attr.freq = 0;
> > evsel->core.attr.sample_period = arm_spe_pmu__sample_period(evsel->pmu);
> > @@ -288,9 +288,10 @@ static void arm_spe_setup_evsel(struct evsel *evsel, struct perf_cpu_map *cpus)
> > * inform that the resulting output's SPE samples contain physical addresses
> > * where applicable.
> > */
> > - bit = perf_pmu__format_bits(evsel->pmu, "pa_enable");
> > - if (evsel->core.attr.config & bit)
> > - evsel__set_sample_bit(evsel, PHYS_ADDR);
> > +
> > + if (!evsel__get_config_val(evsel->pmu, evsel, "pa_enable", &pa_enable_bit))
> > + if (pa_enable_bit)
> > + evsel__set_sample_bit(evsel, PHYS_ADDR);
>
> Hmm... I am a bit concerned for the evsel__get_config_val() usage
> throughout the series.
>
> evsel__get_config_val() returns a whole config value rather than the
> bit field specified by the format name. If other bits (but not the
> "pa_enable" bit) are set in the same config set, would it wrongly set
> the PHYS_ADDR sample bit?
I saw you used FIELD_GET() to read specific bit field in
evsel__get_config_val(). This is not concerned anymore.
Sorry for noise.
> Seems to me, for reading specific format, perf_pmu__format_bits() is
> more suitable than evsel__get_config_val().
For me, this comment is still valid, given perf_pmu__format_bits()
will always exist.
Thanks,
Leo
next prev parent reply other threads:[~2025-12-02 12:42 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
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 [this message]
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=20251202124240.GA724103@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=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).