From: Namhyung Kim <namhyung@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
kernel-team@lge.com
Subject: Re: [RFC] perf script: callchain handling is not useful
Date: Thu, 30 Aug 2018 09:33:27 +0900 [thread overview]
Message-ID: <20180830003327.GA3164@sejong> (raw)
In-Reply-To: <CABPqkBQ1iTg3bkovUykg86r0kj6jaVbb_f=BCVHrLN+=S5jVZQ@mail.gmail.com>
Hi,
On Wed, Aug 29, 2018 at 08:14:12AM -0700, Stephane Eranian wrote:
> On Wed, Aug 29, 2018 at 6:54 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > Em Tue, Aug 28, 2018 at 07:41:31PM -0700, Stephane Eranian escreveu:
> > > Hi,
> > >
> > > I am doing the following simple collection with callchain and load profiling:
> > >
> > > $ perf record -g -d -e cpu/event=0xd0,umask=0x81/pp my_test_program
> > >
> > > But when I type:
> > > $ perf script -F ip,addr
> > > ffff9d4821346878
> > > ffffffff9d58df25
> > > ffffffff9d58e054
> > > ffffffff9d5965bb
> > > ffffffff9d640650
> > > ffffffff9d697d06
> > > ffffffff9d63ec60
> > > ffffffff9d640322
> > > ffffffff9d64070c
> > > ffffffff9d455a60
> > > 7030c7
> > >
> > > ffff9d4638ba84a0
> > > ffffffff9d5df447
> > > ffffffff9d5eaf4a
> > > ffffffff9d63e165
> > > ffffffff9d63e439
> > > ffffffff9d697d98
> > > ffffffff9d63ec60
> > > ffffffff9d640322
> > > ffffffff9d64070c
> > > ffffffff9d455a60
> > > 7030c7
> > > I also see the callchain and it is not clear which is the IP. Further
> > > more parsing becomes more difficult because of multiple lines per
> > > sample. I understand that multiline is likely because of
> > > symbolization. But if I don't want symbolization, it should be
> > > possible to print all in one line.
> >
> > Humm, to have this not break possibly existing scripts, perhaps we can
> > have something like:
> >
> > $ perf script -F ip,-callchain,addr
> >
> > ?
> >
> > And if asked explicitely for the callchain, then it gets added in the
> > same line?
> >
> Yeah, that should do it.
> Thanks.
I found this:
$ perf script -h |& grep -A1 hide
-G, --hide-call-graph
When printing symbols do not display call chain
Thanks,
Namhyung
next prev parent reply other threads:[~2018-08-30 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 2:41 [RFC] perf script: callchain handling is not useful Stephane Eranian
2018-08-29 13:54 ` Arnaldo Carvalho de Melo
2018-08-29 15:14 ` Stephane Eranian
2018-08-30 0:33 ` Namhyung Kim [this message]
2018-08-30 5:01 ` Stephane Eranian
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=20180830003327.GA3164@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.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