From: Jiri Olsa <jolsa@redhat.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: perf script doesn't dump a normal call trace
Date: Mon, 5 Nov 2018 09:49:06 +0100 [thread overview]
Message-ID: <20181105084906.GA30951@krava> (raw)
In-Reply-To: <CADvbK_cgp7S-8Q-6GArwViCDBhCoB9LcZvJaGM6QFAg9qNOeHw@mail.gmail.com>
On Mon, Nov 05, 2018 at 03:20:15PM +0900, Xin Long wrote:
SNIP
> > > > [root@ibm-x3650m4-02 perf]# ./perf probe 'consume_skb'
> > > > [root@ibm-x3650m4-02 perf]# ./perf record -g -e probe:consume_skb* -aR ^C
> > > >
> > > Thanks Jiri,
> > >
> > > My debugging script is using tracepoint with some filters which I
> > > don't think probe can support.
> > > Any one have fixes for this tracepoint issue?
> >
> > trying to bisect that.. looks like orc code issue,
> > it works for me when you switch to fp unwind:
> > CONFIG_UNWINDER_FRAME_POINTER
> >
>
> That's a good workaround, thanks.
>
> Another problem is when I'm using perf built manually from upstream kernel tree,
> I couldn't see the function's names.
> # perf --version
> perf version 4.19.g26f1de
>
> # perf report -T
> # To display the perf.data header info, please use
> --header/--header-only options.
> #
> #
> # Total Lost Samples: 0
> #
> # Samples: 97 of event 'probe:consume_skb'
> # Event count (approx.): 97
> #
> # Children Self Trace output
> # ........ ........ ..................
> #
> 100.00% 100.00% (ffffffff86f090f0)
> |
> |--93.81%--0xffffffff868000e6
> | 0xffffffff8684ed7f
> | 0xffffffff868e97ad
> | 0xffffffff868e953a
> | 0xffffffff87087623
> | 0xffffffff8682a06f
> | 0xffffffff870872ad
> | |
> | |--89.69%--0xffffffff8720098f
> | | 0xffffffff87201b69
> | | 0xffffffff868b9c2e
>
>
> The below is with rhel7's perf
> # perf --version
> perf version 3.10.0-957.el7.x86_64.debug
> # perf report -T
> # To display the perf.data header info, please use
> --header/--header-only options.
> #
> #
> # Total Lost Samples: 0
> #
> # Samples: 97 of event 'probe:consume_skb'
> # Event count (approx.): 97
> #
> # Children Self Trace output
> # ........ ........ ..................
> #
> 100.00% 100.00% (ffffffff86f090f0)
> |
> |--93.81%--0x2000e6
> | start_secondary
> | cpu_startup_entry
> | do_idle
> | default_idle_call
> | arch_cpu_idle
> | default_idle
> | |
> | |--89.69%--ret_from_intr
> | | do_IRQ
> | | irq_exit
I think that's already fixed on Arnaldo's perf/urgent branch,
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
but perhaps this post as well:
https://lore.kernel.org/lkml/20181031091043.23465-1-adrian.hunter@intel.com/
please give it a try.. it should be merged in soon
jirka
next prev parent reply other threads:[~2018-11-05 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 6:36 perf script doesn't dump a normal call trace Xin Long
2018-11-02 10:26 ` Jiri Olsa
2018-11-03 9:36 ` Xin Long
2018-11-04 19:17 ` Jiri Olsa
2018-11-05 6:20 ` Xin Long
2018-11-05 8:49 ` Jiri Olsa [this message]
2018-11-06 8:22 ` Xin Long
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=20181105084906.GA30951@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).