Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934127AbaDIRk2 (ORCPT ); Wed, 9 Apr 2014 13:40:28 -0400 Received: from one.firstfloor.org ([193.170.194.197]:38399 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933114AbaDIRk0 (ORCPT ); Wed, 9 Apr 2014 13:40:26 -0400 Date: Wed, 9 Apr 2014 19:40:24 +0200 From: Andi Kleen To: Andi Kleen Cc: Peter Zijlstra , Andy Lutomirski , David Ahern , Stephane Eranian , "Yan, Zheng" , LKML , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: [PATCH v3 00/14] perf, x86: Haswell LBR call stack support Message-ID: <20140409174024.GB22728@two.firstfloor.org> References: <20140226185513.GL22728@two.firstfloor.org> <530E3E47.8010205@gmail.com> <530E4B42.5090401@gmail.com> <20140409114857.GT11096@twins.programming.kicks-ass.net> <20140409164852.GA22728@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140409164852.GA22728@two.firstfloor.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org BTW the whole discussion is rather pointless. We have to profile the software as it is, not as we wish it to be. That means: small functions, often no frame pointer, all kinds of crappy code and missing information. And then doing it all with as little overhead as possible. I think on these metrics callstack LBR is attractive for many (but not all) cases. -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/