From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753378AbbC3Vxb (ORCPT ); Mon, 30 Mar 2015 17:53:31 -0400 Received: from one.firstfloor.org ([193.170.194.197]:48023 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753318AbbC3Vx3 (ORCPT ); Mon, 30 Mar 2015 17:53:29 -0400 Date: Mon, 30 Mar 2015 23:53:27 +0200 From: Andi Kleen To: Peter Zijlstra Cc: Andi Kleen , "Liang, Kan" , "linux-kernel@vger.kernel.org" , "mingo@kernel.org" , "acme@infradead.org" , "eranian@google.com" Subject: Re: [PATCH V5 4/6] perf, x86: handle multiple records in PEBS buffer Message-ID: <20150330215327.GJ2366@two.firstfloor.org> References: <1424701556-28270-1-git-send-email-kan.liang@intel.com> <1424701556-28270-5-git-send-email-kan.liang@intel.com> <20150330134531.GV23123@twins.programming.kicks-ass.net> <37D7C6CF3E00A74B8858931C1DB2F0770178BAF5@SHSMSX103.ccr.corp.intel.com> <20150330172545.GG2366@two.firstfloor.org> <37D7C6CF3E00A74B8858931C1DB2F0770178BC4D@SHSMSX103.ccr.corp.intel.com> <20150330200710.GO27490@worktop.programming.kicks-ass.net> <20150330201116.GI2366@two.firstfloor.org> <20150330212453.GH23123@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150330212453.GH23123@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I just said I want a > coherent story about what and why we're doing this. What: is clear, isn't it? Use this capability which has been long designed into PEBS, but not used by perf. Why: The goal is to go to higher sampling rates with comparable or less overhead. Higher sampling rates improve analysis of anything that is not mostly doing the same thing over and over. -Andi -- ak@linux.intel.com -- Speaking for myself only.