From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753520AbbLII3e (ORCPT ); Wed, 9 Dec 2015 03:29:34 -0500 Received: from mail-wm0-f46.google.com ([74.125.82.46]:34895 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752519AbbLII32 (ORCPT ); Wed, 9 Dec 2015 03:29:28 -0500 Date: Wed, 9 Dec 2015 09:29:23 +0100 From: Ingo Molnar To: Peter Zijlstra Cc: vincent.weaver@maine.edu, jolsa@redhat.com, torvalds@linux-foundation.org, eranian@google.com, tglx@linutronix.de, acme@redhat.com, ak@linux.intel.com, linux-kernel@vger.kernel.org, hpa@zytor.com, linux-tip-commits@vger.kernel.org Subject: Re: [tip:perf/core] perf/x86: Use INST_RETIRED.PREC_DIST for cycles: ppp Message-ID: <20151209082923.GA15254@gmail.com> References: <1448929689-13771-2-git-send-email-andi@firstfloor.org> <20151206131102.GA12167@gmail.com> <20151207135107.GA6356@twins.programming.kicks-ass.net> <20151208053604.GA15632@gmail.com> <20151208085026.GF6356@twins.programming.kicks-ass.net> <20151208085707.GC6373@twins.programming.kicks-ass.net> <20151208132753.GD6373@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151208132753.GD6373@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Peter Zijlstra wrote: > On Tue, Dec 08, 2015 at 09:57:07AM +0100, Peter Zijlstra wrote: > > On Tue, Dec 08, 2015 at 09:50:26AM +0100, Peter Zijlstra wrote: > > > On Tue, Dec 08, 2015 at 06:36:04AM +0100, Ingo Molnar wrote: > > > > > > > So I checked my NHM box with your latest queue and it now works correctly. Do you > > > > have any idea what the difference is/was? > > > > > > Sadly, no clue :/ > > > > > > I went over those patches and cannot find anything that should affect > > > NHM (or <=SNB in fact). > > > > Oh wait, I spoke too soon, the two new patches affect everything with > > PEBS. And esp. the latter one: > > > > lkml.kernel.org/r/1449177740-5422-2-git-send-email-andi@firstfloor.org > > > > If that is the patch that makes your NHM go again, then running 2 > concurrent perf-top sessions should make it all go dark again. Hm, so I tried again your latest perf/urgent (1221fc3b3e3a) merged into tip:master (c9586e904a68), and booted it on the NHM, but 'perf top' refuses to break. One thing that was special about my first NHM test was that it conducted an about 24 hours perf stress. OTOH 'cycles:p' did work, it was only 'cycles:pp' that was producing no events whatsoever - so it wasn't a total breakage, only :pp related. Weird ... Thanks, Ingo