From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423426AbcFHJI5 (ORCPT ); Wed, 8 Jun 2016 05:08:57 -0400 Received: from mga09.intel.com ([134.134.136.24]:49756 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422828AbcFHJIz (ORCPT ); Wed, 8 Jun 2016 05:08:55 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,438,1459839600"; d="scan'208";a="971298975" Date: Wed, 8 Jun 2016 02:08:54 -0700 From: Andi Kleen To: Stephane Eranian Cc: David Carrillo-Cisneros , LKML , "x86@kernel.org" , Ingo Molnar , "Yan, Zheng" , Kan Liang , Peter Zijlstra Subject: Re: [PATCH 1/3] perf/x86/intel: output LBR support statement after validation Message-ID: <20160608090854.GD9646@tassilo.jf.intel.com> References: <1464835323-33872-1-git-send-email-davidcc@google.com> <1464835323-33872-2-git-send-email-davidcc@google.com> <20160602160428.GR22049@tassilo.jf.intel.com> <20160606015935.GA9646@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.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Ok, so you're saying that syscall and int are not causing LBR callstack to > record an entry. If that is the case, then a rfi should not cause a pop of the > last LBR entry. Is that right? rfi = ? But likely yes. There shouldn't be any ring 0 branches in the callstack LBR, as long as the patch forcing it to ring 3 is still there. -Andi -- ak@linux.intel.com -- Speaking for myself only