From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759454AbcIWLtZ (ORCPT ); Fri, 23 Sep 2016 07:49:25 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48934 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbcIWLtX (ORCPT ); Fri, 23 Sep 2016 07:49:23 -0400 Date: Fri, 23 Sep 2016 13:49:17 +0200 From: Peter Zijlstra To: Alexander Shishkin Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , tglx@linutronix.de, ak@linux.intel.com Subject: Re: [RFC PATCH 0/6] perf: Add AUX data sampling Message-ID: <20160923114917.GI5008@twins.programming.kicks-ass.net> References: <20160923112726.5890-1-alexander.shishkin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160923112726.5890-1-alexander.shishkin@linux.intel.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 23, 2016 at 02:27:20PM +0300, Alexander Shishkin wrote: > Hi Peter, > > This is an RFC, I'm not sending the tooling bits in this series, > although they can be found here [1]. > > This series introduces AUX data sampling for perf events, which in > case of our instruction/branch tracing PMUs like Intel PT, BTS, CS > ETM means execution flow history leading up to a perf event's > overflow. This fails to explain _WHY_ this is a good thing to have. What kind of analysis does this enable, and is that fully implemented in [1] (I didn't look). Please provide a bit more justification.