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: Fri, 2 Nov 2018 11:26:16 +0100 [thread overview]
Message-ID: <20181102102616.GC5458@krava> (raw)
In-Reply-To: <CADvbK_dNN34=5V3qtk3_vBzKNts55ACR4c-erPafgNuAQ-eRuw@mail.gmail.com>
On Fri, Nov 02, 2018 at 03:36:13PM +0900, Xin Long wrote:
> On upstream kernel(4.19) or RHEL-8 kernel(4.18.0):
>
> # perf record -e 'skb:consume_skb' -ag
> ^C[ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.612 MB perf.data (634 samples) ]
>
> # perf script
> swapper 0 [009] 274370.117711: skb:consume_skb: skbaddr=0xffff962c591d5b00
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> kworker/9:1-eve 926 [009] 274370.117729: skb:consume_skb:
> skbaddr=0xffff962c591d5b00
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> kworker/9:1-eve 926 [009] 274370.117732: skb:consume_skb:
> skbaddr=0xffff962c591d4900
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> swapper 0 [009] 274370.145528: skb:consume_skb: skbaddr=0xffff962c591d4900
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> kworker/9:1-eve 926 [009] 274370.145545: skb:consume_skb:
> skbaddr=0xffff962c591d4900
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> kworker/9:1-eve 926 [009] 274370.145547: skb:consume_skb:
> skbaddr=0xffff962c591d5b00
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
>
> swapper 0 [009] 274370.173443: skb:consume_skb: skbaddr=0xffff962c591d5b00
> ffffffffa4abe534 consume_skb+0x64 ([kernel.kallsyms])
I can see that on upstream as well, probably something within
tracepoint entry code, because I have it working nicely when
from kprobe, like:
[root@ibm-x3650m4-02 perf]# ./perf probe 'consume_skb'
[root@ibm-x3650m4-02 perf]# ./perf record -g -e probe:consume_skb* -aR ^C
jirka
next prev parent reply other threads:[~2018-11-02 10:26 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 [this message]
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
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=20181102102616.GC5458@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.