From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Kan Liang <kan.liang@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
James Clark <james.clark@arm.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 0/6] Assume sysfs event names are always the same case
Date: Fri, 3 May 2024 17:09:30 -0300 [thread overview]
Message-ID: <ZjVEeuFPMknYI7_H@x1> (raw)
In-Reply-To: <20240502213507.2339733-1-irogers@google.com>
On Thu, May 02, 2024 at 02:35:01PM -0700, Ian Rogers wrote:
> By assuming sysfs events are either upper or lower case, the case
> insensitive event parsing can probe for the existence of files rather
> then loading all events in a directory. When the event is a json event
> like inst_retired.any on Intel, this reduces the number of openat
> calls on a Tigerlake laptop from 325 down to 255.
Thanks, applied to perf-tools-next,
- Arnaldo
> v1 sent as an RFC:
> https://lore.kernel.org/lkml/20240413040812.4042051-1-irogers@google.com/
>
> v2: addresses review feedback from Kan Liang, by updating
> documentation and adding tests.
>
> v3: incorporate feedback from Thomas Richter <tmricht@linux.ibm.com>
> that s390 event names are all upper case. Do a lower case probe
> then an upper case probe, make documentation and tests also agree.
>
> v4: add checks to write (kernel test robot) and fix a typo.
>
> v5: Add reviewed-by: Kan Liang and fix potential uninitialized use.
>
> Ian Rogers (6):
> perf test pmu-events: Make it clearer that pmu-events tests json
> events
> perf Document: Sysfs event names must be lower or upper case
> perf test pmu: Refactor format test and exposed test APIs
> perf test pmu: Add an eagerly loaded event test
> perf test pmu: Test all sysfs PMU event names are the same case
> perf pmu: Assume sysfs events are always the same case
>
> .../sysfs-bus-event_source-devices-events | 6 +
> tools/perf/tests/pmu-events.c | 2 +-
> tools/perf/tests/pmu.c | 467 ++++++++++++------
> tools/perf/util/parse-events.c | 2 +-
> tools/perf/util/parse-events.h | 2 +-
> tools/perf/util/pmu.c | 111 +++--
> tools/perf/util/pmu.h | 4 +-
> tools/perf/util/pmus.c | 16 +-
> tools/perf/util/pmus.h | 2 +
> 9 files changed, 415 insertions(+), 197 deletions(-)
>
> --
> 2.45.0.rc1.225.g2a3ae87e7f-goog
next prev parent reply other threads:[~2024-05-03 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 21:35 [PATCH v5 0/6] Assume sysfs event names are always the same case Ian Rogers
2024-05-02 21:35 ` [PATCH v5 1/6] perf test pmu-events: Make it clearer that pmu-events tests json events Ian Rogers
2024-05-02 21:35 ` [PATCH v5 2/6] perf Document: Sysfs event names must be lower or upper case Ian Rogers
2024-05-12 22:08 ` Randy Dunlap
2024-05-13 16:22 ` Ian Rogers
2024-05-13 18:54 ` Randy Dunlap
2024-05-02 21:35 ` [PATCH v5 3/6] perf test pmu: Refactor format test and exposed test APIs Ian Rogers
2024-05-02 21:35 ` [PATCH v5 4/6] perf test pmu: Add an eagerly loaded event test Ian Rogers
2024-05-02 21:35 ` [PATCH v5 5/6] perf test pmu: Test all sysfs PMU event names are the same case Ian Rogers
2024-05-02 21:35 ` [PATCH v5 6/6] perf pmu: Assume sysfs events are always " Ian Rogers
2024-05-03 20:09 ` Arnaldo Carvalho de Melo [this message]
2024-05-06 15:34 ` [PATCH v5 0/6] Assume sysfs event names " Thomas Richter
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=ZjVEeuFPMknYI7_H@x1 \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=rdunlap@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=tmricht@linux.ibm.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).