Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751737AbbHSXcY (ORCPT ); Wed, 19 Aug 2015 19:32:24 -0400 Received: from mga11.intel.com ([192.55.52.93]:58208 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbbHSXcW (ORCPT ); Wed, 19 Aug 2015 19:32:22 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,713,1432623600"; d="scan'208";a="772072210" Date: Wed, 19 Aug 2015 16:32:21 -0700 From: Andi Kleen To: Stephane Eranian Cc: LKML , Arnaldo Carvalho de Melo , Peter Zijlstra , "mingo@elte.hu" , Jiri Olsa , Namhyung Kim , "Liang, Kan" , David Ahern , Adrian Hunter Subject: Re: [PATCH v1 4/4] perf script: enable printing of branch stack Message-ID: <20150819233221.GL4524@tassilo.jf.intel.com> References: <1439973506-2166-1-git-send-email-eranian@google.com> <1439973506-2166-5-git-send-email-eranian@google.com> <20150819221147.GK4524@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 601 Lines: 19 > > Also it would be good to resolve the addresses to symbol + offset > > But then, that becomes harder to post-process or even read with long > C++ signatures. Ok. Maybe make it optional? For many usages resolved addresses will be much more useful than raw. Normall call stacks also do that. -Andi -- ak@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/