Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753611AbdCBCup (ORCPT ); Wed, 1 Mar 2017 21:50:45 -0500 Received: from mail-wr0-f169.google.com ([209.85.128.169]:36473 "EHLO mail-wr0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751595AbdCBCun (ORCPT ); Wed, 1 Mar 2017 21:50:43 -0500 MIME-Version: 1.0 From: Joel Fernandes Date: Wed, 1 Mar 2017 16:42:17 -0800 Message-ID: Subject: ARM64 perf stacktraces on tracepoint events To: Linux Kernel Mailing List Cc: peterz@infradead.org, acme@kernel.org, alexander.shishkin@linux.intel.com, mingo@redhat.com, Linux ARM Kernel List , bgregg@netflix.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1104 Lines: 41 Hi, On 3.18 kernel running on an arm64 device, I tried running: perf record -a -g -e sched:sched_wakeup I was expecting something like the output at: www.brendangregg.com/perf.html But I don't see stacktraces, could I be missing any patches you could point me to? I do see stack traces if I do regular perf profiling (perf record -F 99 -a -g). Below is the output I get. Thanks for any insight into this. Regards, Joel sailfish:/data # ./perf report # Samples: 22 of event 'sched:sched_wakeup' # Event count (approx.): 410333 # # Children Self Trace output # ........ ........ ............................................................. # 61.29% 61.29% comm=ksoftirqd/0 pid=3 prio=120 success=1 target_cpu=000 | ---0 33.25% 33.25% comm=hw pid=12777 prio=120 success=1 target_cpu=002 | ---0 2.46% 2.46% comm=kworker/u8:2 pid=12482 prio=120 success=1 target_cpu=002 | ---0 1.39% 1.39% comm=migration/2 pid=21 prio=0 success=1 target_cpu=002 | ---0