Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755840AbcLUW5o (ORCPT ); Wed, 21 Dec 2016 17:57:44 -0500 Received: from mga02.intel.com ([134.134.136.20]:26943 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755182AbcLUW4c (ORCPT ); Wed, 21 Dec 2016 17:56:32 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,385,1477983600"; d="scan'208";a="45558351" Subject: Re: Inlined functions in perf report To: "Steinar H. Gunderson" , Milian Wolff References: <20161220115954.GA35897@sesse.net> <20161221095823.GA19249@sesse.net> <8193556.VWj3dM7HSI@milian-kdab2> <20161221102035.GA31703@sesse.net> Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Jiri Olsa , "Liang, Kan" From: "Jin, Yao" Message-ID: <499d963f-9049-0b6c-00c3-0f155433ae26@linux.intel.com> Date: Thu, 22 Dec 2016 06:56:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161221102035.GA31703@sesse.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 35 Could you see the inline if you use the addr2line command? For example, addr2line -e -i For example, in my case, root@skl:/home/jinyao/skl-ws/perf-dev/lck-2867/test# addr2line -e ./test2 -i 40052d /usr/include/x86_64-linux-gnu/bits/stdio2.h:104 /home/jinyao/skl-ws/perf-dev/lck-2867/test/test2.c:27 /home/jinyao/skl-ws/perf-dev/lck-2867/test/test2.c:35 /home/jinyao/skl-ws/perf-dev/lck-2867/test/test2.c:45 /home/jinyao/skl-ws/perf-dev/lck-2867/test/test2.c:61 00000000004004f0
: ...... 40052d: e8 6e ff ff ff callq 4004a0 Thanks Jin Yao On 12/21/2016 6:20 PM, Steinar H. Gunderson wrote: > On Wed, Dec 21, 2016 at 11:09:42AM +0100, Milian Wolff wrote: >> Just to check - did you really compile your code with frame pointers? By >> default, that is not the case, and the above will try to do frame pointer >> unwinding which will then fail. Put differently - do you any stack frames at >> all? Can you try `perf record --call-graph dwarf` instead? Of course, make >> sure you compile your code with `-g -O2` or similar. > I don't specifically use -fno-omit-frame-pointer, no. But the normal stack > unwinding works just fine with mainline perf nevertheless; is this expected? > > /* Steinar */