From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>
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,
James Clark <james.clark@linaro.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: Thu, 17 Oct 2024 09:39:21 -0700 [thread overview]
Message-ID: <172918316105.639809.18120373431908950671.b4-ty@kernel.org> (raw)
In-Reply-To: <20241016065654.269994-1-namhyung@kernel.org>
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
prev parent reply other threads:[~2024-10-17 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 6:56 Namhyung Kim
2024-10-16 8:25 ` James Clark
2024-10-16 14:55 ` Ian Rogers
2024-10-17 16:39 ` Namhyung Kim [this message]
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=172918316105.639809.18120373431908950671.b4-ty@kernel.org \
--to=namhyung@kernel.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=james.clark@linaro.org \
--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=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
all inboxes | Powered by JetHome®