Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751869AbdFPTPR (ORCPT ); Fri, 16 Jun 2017 15:15:17 -0400 Received: from mail-io0-f180.google.com ([209.85.223.180]:36804 "EHLO mail-io0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750903AbdFPTPP (ORCPT ); Fri, 16 Jun 2017 15:15:15 -0400 MIME-Version: 1.0 In-Reply-To: <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> <20170616175020.GF4789@tassilo.jf.intel.com> From: Stephane Eranian Date: Fri, 16 Jun 2017 12:15:14 -0700 Message-ID: Subject: Re: [PATCH 0/5] perf: add support for capturing skid IP To: Andi Kleen Cc: LKML , Arnaldo Carvalho de Melo , Peter Zijlstra , "mingo@elte.hu" , "Liang, Kan" , Jiri Olsa Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 553 Lines: 14 On Fri, Jun 16, 2017 at 10:50 AM, Andi Kleen wrote: >> > 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. > That's on Intel X86. What about the other arch? > -Andi