From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v2 2/2] perf stat: Support regex pattern in --for-each-cgroup
Date: Mon, 26 Oct 2020 12:40:09 +0100 [thread overview]
Message-ID: <20201026114009.GD2726983@krava> (raw)
In-Reply-To: <20201024025918.453431-2-namhyung@kernel.org>
On Sat, Oct 24, 2020 at 11:59:18AM +0900, Namhyung Kim wrote:
> To make the command line even more compact with cgroups, support regex
> pattern matching in cgroup names.
>
> $ perf stat -a -e cpu-clock,cycles --for-each-cgroup ^foo sleep 1
>
> 3,000.73 msec cpu-clock foo # 2.998 CPUs utilized
> 12,530,992,699 cycles foo # 7.517 GHz (100.00%)
> 1,000.61 msec cpu-clock foo/bar # 1.000 CPUs utilized
> 4,178,529,579 cycles foo/bar # 2.506 GHz (100.00%)
> 1,000.03 msec cpu-clock foo/baz # 0.999 CPUs utilized
> 4,176,104,315 cycles foo/baz # 2.505 GHz (100.00%)
just curious.. there was another foo/XXX group using the
rest of the cycles, right?
also perhaps we want to warn if there's no match found:
$ sudo ./perf stat -a -e cpu-clock,cycles --for-each-cgroup ^foo sleep 1
Performance counter stats for 'system wide':
1.002375575 seconds time elapsed
jirka
next prev parent reply other threads:[~2020-10-26 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 2:59 [PATCH 1/2] perf test: Use generic event for expand_libpfm_events() Namhyung Kim
2020-10-24 2:59 ` [PATCH v2 2/2] perf stat: Support regex pattern in --for-each-cgroup Namhyung Kim
2020-10-26 11:40 ` Jiri Olsa [this message]
2020-10-26 12:32 ` Namhyung Kim
2020-10-26 13:12 ` Jiri Olsa
2020-10-26 17:53 ` Arnaldo Carvalho de Melo
2020-10-27 5:00 ` Namhyung Kim
2020-10-25 5:30 ` [PATCH 1/2] perf test: Use generic event for expand_libpfm_events() Andi Kleen
2020-10-26 15:40 ` Ian Rogers
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=20201026114009.GD2726983@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@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).