linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: 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>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: perf script doesn't dump a normal call trace
Date: Fri, 2 Nov 2018 15:36:13 +0900	[thread overview]
Message-ID: <CADvbK_dNN34=5V3qtk3_vBzKNts55ACR4c-erPafgNuAQ-eRuw@mail.gmail.com> (raw)

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])


On RHEL-7 kernel(3.10.0):

# perf record -e 'skb:consume_skb' -ag
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.170 MB perf.data (214 samples) ]

# perf script
swapper     0 [001] 69006.726193: skb:consume_skb: skbaddr=0xffff917db9647900
            7fffb3425a00 consume_skb ([kernel.kallsyms])
            7fffb34ba3cb arp_process ([kernel.kallsyms])
            7fffb34bad65 arp_rcv ([kernel.kallsyms])
            7fffb343b6d9 __netif_receive_skb_core ([kernel.kallsyms])
            7fffb343b9d8 __netif_receive_skb ([kernel.kallsyms])
            7fffb343ba60 netif_receive_skb_internal ([kernel.kallsyms])
            7fffb343c6e8 napi_gro_receive ([kernel.kallsyms])
            7fffc007d1f5 virtnet_poll ([kernel.kallsyms])
            7fffb343c07f net_rx_action ([kernel.kallsyms])
            7fffb2ea2f05 __do_softirq ([kernel.kallsyms])
            7fffb357a32c call_softirq ([kernel.kallsyms])
            7fffb2e30675 do_softirq ([kernel.kallsyms])
            7fffb2ea3285 irq_exit ([kernel.kallsyms])
            7fffb357b5e6 __irqentry_text_start ([kernel.kallsyms])
            7fffb356d362 ret_from_intr ([kernel.kallsyms])
            7fffb356c12e default_idle ([kernel.kallsyms])
            7fffb2e386f0 arch_cpu_idle ([kernel.kallsyms])
            7fffb2efe3ba cpu_startup_entry ([kernel.kallsyms])
            7fffb2e59db7 start_secondary ([kernel.kallsyms])
            7fffb2e020d5 start_cpu ([kernel.kallsyms])

swapper     0 [001] 69006.754090: skb:consume_skb: skbaddr=0xffff917db9647100
            7fffb3425a00 consume_skb ([kernel.kallsyms])
            7fffb34ba3cb arp_process ([kernel.kallsyms])
            7fffb34bad65 arp_rcv ([kernel.kallsyms])
            7fffb343b6d9 __netif_receive_skb_core ([kernel.kallsyms])
            7fffb343b9d8 __netif_receive_skb ([kernel.kallsyms])
            7fffb343ba60 netif_receive_skb_internal ([kernel.kallsyms])
            7fffb343c6e8 napi_gro_receive ([kernel.kallsyms])
            7fffc007d1f5 virtnet_poll ([kernel.kallsyms])
            7fffb343c07f net_rx_action ([kernel.kallsyms])
            7fffb2ea2f05 __do_softirq ([kernel.kallsyms])
            7fffb357a32c call_softirq ([kernel.kallsyms])
            7fffb2e30675 do_softirq ([kernel.kallsyms])
            7fffb2ea3285 irq_exit ([kernel.kallsyms])
            7fffb357b5e6 __irqentry_text_start ([kernel.kallsyms])
            7fffb356d362 ret_from_intr ([kernel.kallsyms])
            7fffb356c12e default_idle ([kernel.kallsyms])
            7fffb2e386f0 arch_cpu_idle ([kernel.kallsyms])
            7fffb2efe3ba cpu_startup_entry ([kernel.kallsyms])


any idea why I could get a proper call trace on the new kernel?

Thanks.

             reply	other threads:[~2018-11-02  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02  6:36 Xin Long [this message]
2018-11-02 10:26 ` perf script doesn't dump a normal call trace 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
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='CADvbK_dNN34=5V3qtk3_vBzKNts55ACR4c-erPafgNuAQ-eRuw@mail.gmail.com' \
    --to=lucien.xin@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --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).