From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751191AbeCII5f (ORCPT ); Fri, 9 Mar 2018 03:57:35 -0500 Received: from terminus.zytor.com ([198.137.202.136]:57573 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751054AbeCII5e (ORCPT ); Fri, 9 Mar 2018 03:57:34 -0500 Date: Fri, 9 Mar 2018 00:57:13 -0800 From: tip-bot for Wang YanQing Message-ID: Cc: udknight@gmail.com, peterz@infradead.org, alexander.shishkin@linux.intel.com, mingo@kernel.org, hpa@zytor.com, tglx@linutronix.de, jolsa@kernel.org, jolsa@redhat.com, linux-kernel@vger.kernel.org, acme@redhat.com Reply-To: udknight@gmail.com, alexander.shishkin@linux.intel.com, peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org, hpa@zytor.com, jolsa@kernel.org, jolsa@redhat.com, linux-kernel@vger.kernel.org, acme@redhat.com In-Reply-To: <20180308032850.GA12383@udknight-ThinkPad-E550> References: <20180308032850.GA12383@udknight-ThinkPad-E550> To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/core] perf report: Provide libtraceevent with a kernel symbol resolver Git-Commit-ID: ea85ab24c502720d2eb3dec30bedb6df06d4900b X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: ea85ab24c502720d2eb3dec30bedb6df06d4900b Gitweb: https://git.kernel.org/tip/ea85ab24c502720d2eb3dec30bedb6df06d4900b Author: Wang YanQing AuthorDate: Thu, 8 Mar 2018 11:28:50 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Mar 2018 11:30:51 -0300 perf report: Provide libtraceevent with a kernel symbol resolver So that beautifiers wanting to resolve kernel function addresses to names can do its work, and when we use "perf report" for output of "perf kmem record", we will get kernel symbol output. This patch affect the output of "perf report" for the record data generated by "perf kmem record" looks like below: Before patch: 0.01% call_site=ffffffff814e5828 ptr=0x99bb000 bytes_req=3616 bytes_alloc=4096 gfp_flags=GFP_ATOMIC 0.01% call_site=ffffffff81370b87 ptr=0x428a3060 bytes_req=32 bytes_alloc=32 gfp_flags=GFP_KERNEL|GFP_ZERO After patch: 0.01% (aa_alloc_task_context+0x27) call_site=ffffffff81370b87 ptr=0x428a3060 bytes_req=32 bytes_alloc=32 gfp_flags=GFP_KERNEL|GFP_ZERO 0.01% (__tty_buffer_request_room+0x88) call_site=ffffffff814e5828 ptr=0x99bb000 bytes_req=3616 bytes_alloc=4096 gfp_flags=GFP_ATOMIC Signed-off-by: Wang YanQing Acked-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/20180308032850.GA12383@udknight-ThinkPad-E550 Signed-off-by: Arnaldo Carvalho de Melo --- tools/perf/builtin-report.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c index c3603d4c0c57..971ccba85464 100644 --- a/tools/perf/builtin-report.c +++ b/tools/perf/builtin-report.c @@ -1348,6 +1348,15 @@ repeat: report.range_num = 1; } + if (session->tevent.pevent && + pevent_set_function_resolver(session->tevent.pevent, + machine__resolve_kernel_addr, + &session->machines.host) < 0) { + pr_err("%s: failed to set libtraceevent function resolver\n", + __func__); + return -1; + } + sort__setup_elide(stdout); ret = __cmd_report(&report);