From: James Clark <james.clark@linaro.org>
To: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Leo Yan <leo.yan@arm.com>,
German Gomez <german.gomez@arm.com>,
Carsten Haitzler <carsten.haitzler@arm.com>
Subject: Re: [PATCH] perf test: Speed up some tests using perf list
Date: Wed, 16 Oct 2024 09:25:41 +0100 [thread overview]
Message-ID: <c28ce930-9a70-4f23-9f6b-541c16c212e3@linaro.org> (raw)
In-Reply-To: <20241016065654.269994-1-namhyung@kernel.org>
On 16/10/2024 7:56 am, Namhyung Kim wrote:
> On my system, perf list is very slow to print the whole events. I think
> there's a performance issue in SDT and uprobes event listing. I noticed
> this issue while running perf test on x86 but it takes long to check
> some CoreSight event which should be skipped quickly.
>
> Anyway, some test uses perf list to check whether the required event is
> available before running the test. The perf list command can take an
> argument to specify event class or (glob) pattern. But glob pattern is
> only to suppress output for unmatched ones after checking all events.
>
> In this case, specifying event class is better to reduce the number of
> events it checks and to avoid buggy subsystems entirely.
>
> No functional changes intended.
>
> Cc: German Gomez <german.gomez@arm.com>
> Cc: Carsten Haitzler <carsten.haitzler@arm.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
Reviewed-by: James Clark <james.clark@linaro.org>
next prev parent reply other threads:[~2024-10-16 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 6:56 [PATCH] perf test: Speed up some tests using perf list Namhyung Kim
2024-10-16 8:25 ` James Clark [this message]
2024-10-16 14:55 ` Ian Rogers
2024-10-17 16:39 ` Namhyung Kim
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=c28ce930-9a70-4f23-9f6b-541c16c212e3@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=carsten.haitzler@arm.com \
--cc=german.gomez@arm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).