[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190930182136.GD8560@tassilo.jf.intel.com>
Date: Mon, 30 Sep 2019 11:21:36 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Jin Yao <yao.jin@...ux.intel.com>, acme@...nel.org,
jolsa@...nel.org, peterz@...radead.org, mingo@...hat.com,
alexander.shishkin@...ux.intel.com, Linux-kernel@...r.kernel.org,
kan.liang@...el.com, yao.jin@...el.com
Subject: Re: [PATCH v1 0/2] perf stat: Support --all-kernel and --all-user
On Sun, Sep 29, 2019 at 05:29:13PM +0200, Jiri Olsa wrote:
> On Wed, Sep 25, 2019 at 10:02:16AM +0800, Jin Yao wrote:
> > This patch series supports the new options "--all-kernel" and "--all-user"
> > in perf-stat.
> >
> > For example,
> >
> > root@kbl:~# perf stat -e cycles,instructions --all-kernel --all-user -a -- sleep 1
> >
> > Performance counter stats for 'system wide':
> >
> > 19,156,665 cycles:k
> > 7,265,342 instructions:k # 0.38 insn per cycle
> > 4,511,186,293 cycles:u
> > 121,881,436 instructions:u # 0.03 insn per cycle
>
> hi,
> I think we should follow --all-kernel/--all-user behaviour from record
> command, adding extra events seems like unnecesary complexity to me
I think it's useful. Makes it easy to do kernel/user break downs.
perf record should support the same.
-Andi
Powered by blists - more mailing lists