public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf tools: Introduce new -P/--parent-deep report option
Date: Wed, 26 Jun 2013 11:58:53 -0300	[thread overview]
Message-ID: <20130626145853.GA2309@ghostprotocols.net> (raw)

Hi Jiri,

	About the patch below, can't this be solved by using a regex
instead of a simple substring search instead of adding a new command
line option?

- Arnaldo

commit 5b42ff035ec784c5c42c4a6bb9e7fada882f097e
Author: Jiri Olsa <jolsa@redhat.com>
Date:   Tue Jun 18 18:31:50 2013 +0200

    perf tools: Introduce new -P/--parent-deep report option
    
    Introducing new -P/--parent-deep report option. It does the
    same as '-p' but it force the deep search of the callchain
    and looks for the deepest possible match.
    
    The -p option searches for the first match of the parent
    pattern in the callchain.
    
      $ perf report -i perf.data.delete -p perf_session__delete -s parent
    
      +  99.51%  [other]
      +   0.46%  perf_session__delete_dead_threads
      +   0.03%  perf_session__delete
      +   0.00%  perf_session__delete_threads
    
    so we got multiple 'different' matches instancies, while
    they all belong under perf_session__delete function:
    
      $ perf report -i perf.data.delete -P perf_session__delete -s parent
    
      +  99.51%  [other]
      +   0.49%  perf_session__delete
    
    NOTE the 'p' vs 'P' difference in above commands above.


             reply	other threads:[~2013-06-26 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 14:58 Arnaldo Carvalho de Melo [this message]
2013-06-27  5:29 ` perf tools: Introduce new -P/--parent-deep report option Namhyung Kim
2013-06-27  9:21   ` Jiri Olsa

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=20130626145853.GA2309@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.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