[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172918316105.639809.18120373431908950671.b4-ty@kernel.org>
Date: Thu, 17 Oct 2024 09:39:21 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ian Rogers <irogers@...gle.com>, Kan Liang <kan.liang@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, linux-perf-users@...r.kernel.org,
James Clark <james.clark@...aro.org>, Leo Yan <leo.yan@....com>,
German Gomez <german.gomez@....com>,
Carsten Haitzler <carsten.haitzler@....com>
Subject: Re: [PATCH] perf test: Speed up some tests using perf list
On Tue, 15 Oct 2024 23:56:54 -0700, 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.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists