From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753357AbcAGV7v (ORCPT ); Thu, 7 Jan 2016 16:59:51 -0500 Received: from mail.kernel.org ([198.145.29.136]:56178 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752015AbcAGV7u (ORCPT ); Thu, 7 Jan 2016 16:59:50 -0500 Date: Thu, 7 Jan 2016 18:59:45 -0300 From: Arnaldo Carvalho de Melo To: Stephane Eranian Cc: LKML , Jiri Olsa , Namhyung Kim , Peter Zijlstra , Ingo Molnar , Adrian Hunter , "ak@linux.intel.com" Subject: Re: [RFC] perf record: missing buildid for callstack modules Message-ID: <20160107215945.GA19314@kernel.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, Jan 07, 2016 at 01:56:14PM -0800, Stephane Eranian escreveu: > Hi, > > Whenever you do: > > $ perf record -g -a sleep 10 > > Perf will collect the callstack for each sample. At the end of the > run, perf record > adds the buildid for all dso with at least one sample. But when it does this, it > only looks at the sampled IP and ignore the modules traversed by the callstack. > That means that, it is not possible to uniquely identify the modules executed, > unless they had at least one IP sample captured. But this is not > always the case. > > How about providing an option to perf record to force collecting > buildid for all IPs > captured in the callstack? I understand that would cost more at the end of the > collection, but this would be beneficial to several monitoring scenarios. I agree, would consider applying a patch that provides the option but does not do this by default. - Arnaldo