From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756186Ab0BCOmT (ORCPT ); Wed, 3 Feb 2010 09:42:19 -0500 Received: from bombadil.infradead.org ([18.85.46.34]:43961 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753504Ab0BCOmS (ORCPT ); Wed, 3 Feb 2010 09:42:18 -0500 Subject: Re: [RFC][PATCH] perf_events, x86: PEBS support From: Peter Zijlstra To: Stephane Eranian Cc: Ingo Molnar , Paul Mackerras , "Metzger, Markus T" , lkml , Robert Richter , "David S. Miller" , Jamie Iles , Paul Mundt , Arjan van de Ven , "H. Peter Anvin" , perfmon2-devel@lists.sf.net In-Reply-To: References: <1265129772.24455.329.camel@laptop> <20100202182653.GB19320@elte.hu> <1265135588.24455.350.camel@laptop> <1265205361.24455.533.camel@laptop> <1265206784.24455.568.camel@laptop> Content-Type: text/plain; charset="UTF-8" Date: Wed, 03 Feb 2010 15:40:12 +0100 Message-ID: <1265208012.24455.592.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2010-02-03 at 15:30 +0100, Stephane Eranian wrote: > On Wed, Feb 3, 2010 at 3:19 PM, Peter Zijlstra wrote: > > On Wed, 2010-02-03 at 15:07 +0100, Stephane Eranian wrote: > >> >> The only improvement that PEBS provides is that you get an IP and the > >> >> machine state at retirement of an instruction that caused the event to > >> >> increment. Thus, the IP points to the next dynamic instruction. The instruction > >> >> is not the one that cause the P-th occurence of the event, if you set the > >> >> period to P. It is at P+N, where N cannot be predicted and varies depending > >> >> on the event and executed code. This introduces some bias in the samples.. > >> > > >> > I'm not sure I follow, it records the next event after overflow, doesn't > >> > that make it P+1? > >> > > >> That is not what I wrote. I did not say if records at P+1. I said it records > >> at P+N, where N varies from sample to sample and cannot be predicted. > >> N is expressed in the unit of the sampling event. > > > > OK, so I'm confused. > > > > The manual says it arms the PEBS assist on overflow, and the PEBS thing > > will then record the next event. Which to me reads like P+1. > > > you are assuming arming is instantaneous. Yes I was, ok that stinks. If only they would reset the counter on overflow instead of on record, that would solve quite a few issues I imagine. Then add IP to the actual instruction and you've got yourself a useful tool :-)