Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752690AbdFPRuX (ORCPT ); Fri, 16 Jun 2017 13:50:23 -0400 Received: from mga01.intel.com ([192.55.52.88]:59975 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751958AbdFPRuV (ORCPT ); Fri, 16 Jun 2017 13:50:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,348,1493708400"; d="scan'208";a="98713716" Date: Fri, 16 Jun 2017 10:50:20 -0700 From: Andi Kleen To: Stephane Eranian Cc: LKML , Arnaldo Carvalho de Melo , Peter Zijlstra , "mingo@elte.hu" , "Liang, Kan" , Jiri Olsa Subject: Re: [PATCH 0/5] perf: add support for capturing skid IP Message-ID: <20170616175020.GF4789@tassilo.jf.intel.com> References: <20170615172320.GB4789@tassilo.jf.intel.com> <20170615200205.GC4789@tassilo.jf.intel.com> <20170615231816.GD4789@tassilo.jf.intel.com> <20170616160630.GE4789@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.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 417 Lines: 11 > > Yeah, I think it is easier and more portable, especially on hardware with a > > PEBS-like mechanism but no branch buffer (like LBR). FYI, I did do a test > > implementation yesterday to evaluate the difficulty. > > > A more generalized usage of the feature is to evaluate the amount of skid > for any precise event. It should be always the same (one instruction), except for the control flow change case. -Andi