public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2] perf stat: Append to default list if use -e +event
Date: Thu, 21 Jan 2021 10:02:25 -0300	[thread overview]
Message-ID: <20210121130225.GV12699@kernel.org> (raw)
In-Reply-To: <2d2c8e32-53f2-560d-3f69-a0ed7c3810e6@linux.intel.com>

Em Thu, Jan 21, 2021 at 02:08:52PM +0800, Jin, Yao escreveu:
> Hi Arnaldo,
> 
> On 1/21/2021 8:03 AM, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Jan 20, 2021 at 10:25:53PM +0100, Jiri Olsa escreveu:
> > > On Mon, Jan 18, 2021 at 12:54:37PM +0800, Jin, Yao wrote:
> > > > root@kbl-ppc:# ./perf stat -e +power/energy-pkg/ -a -- sleep 1
> > 
> > > >   Performance counter stats for 'system wide':
> > 
> > > >                2.02 Joules +power/energy-pkg/
> > 
> > > >         1.000859434 seconds time elapsed
> > 
> > > > The '+' prefix is printed. So I finally decide not to remove the '+' prefix
> > > > in order to keep original behavior.
> > > hm, originaly there's no purpose for the '+', right?
> > > it seems it's more like bug then anything else
> > > you added function to the '+' to add default events to specified event,
> > > which I think is good idea, but I don't think we should display the
> > > extra '+' in output
> > 
> > The value would be to stress that that is an event added to the ones
> > without the + prefix, i.e. the default ones.
> > 
> > But by having the command line copied over and the added events at the
> > first lines we should have that abundantly clear.
> > 
> > Also we won't print removed events (using -), is that available already?
> > 
> 
> Sorry, the '-' support is not available in this patch. Can I do the patch
> for '+' first and then do a follow up patch for '-' at next step?

Yeah, it can be done afterwards, to be symmetric.
 
> > Nope:
> > 
> > [root@quaco ~]# perf stat -e -cycles sleep
> > event syntax error: '-cycles'
> >                       \___ parser error
> > Run 'perf list' for a list of valid events
> > 
> >   Usage: perf stat [<options>] [<command>]
> > 
> >      -e, --event <event>   event selector. use 'perf list' to list available events
 
> So if we just want to append the default list, we only need to set
> detailed_run=1, then ideally perf-stat will print the default list.
 
> But for now, there are no task-clock, context-switches, cpu-migrations,
> page-faults, instructions, branches and branch-misses displayed.
 
> root@kbl-ppc:~# ./perf stat -e cycles -d -a -- sleep 1
> 
>  Performance counter stats for 'system wide':
> 
>        124,178,207      cycles                                                        (80.02%)
>          6,444,490      L1-dcache-loads                                               (80.01%)
>          1,043,169      L1-dcache-load-misses     #   16.19% of all L1-dcache accesses  (80.02%)
>            564,474      LLC-loads                                                     (80.02%)
>             49,262      LLC-load-misses           #    8.73% of all LL-cache accesses  (79.92%)
> 
>        1.001614947 seconds time elapsed
> 
> Do we still need the '+' prefix to add the specified event on top of default
> list? It looks current syntax should already support that feature, but just
> need to fix some issues.

I think we can do away with that '+' when showing the added events and
its counts.

- Arnaldo

  reply	other threads:[~2021-01-21 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04  2:18 [PATCH v2] perf stat: Append to default list if use -e +event Jin Yao
2021-01-12 10:08 ` Jiri Olsa
2021-01-18  4:54   ` Jin, Yao
2021-01-20 21:25     ` Jiri Olsa
2021-01-21  0:03       ` Arnaldo Carvalho de Melo
2021-01-21  6:08         ` Jin, Yao
2021-01-21 13:02           ` Arnaldo Carvalho de Melo [this message]
2021-01-22  1:43             ` Jin, Yao
2021-01-23 23:14             ` Jiri Olsa
2021-01-21  5:05       ` Jin, Yao

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=20210121130225.GV12699@kernel.org \
    --to=acme@kernel.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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