From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755946Ab0IJQm7 (ORCPT ); Fri, 10 Sep 2010 12:42:59 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:47953 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755872Ab0IJQm4 (ORCPT ); Fri, 10 Sep 2010 12:42:56 -0400 Date: Fri, 10 Sep 2010 18:42:24 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Robert Richter , Don Zickus , "gorcunov@gmail.com" , "fweisbec@gmail.com" , "linux-kernel@vger.kernel.org" , "ying.huang@intel.com" , "ming.m.lin@intel.com" , "yinghai@kernel.org" , "andi@firstfloor.org" , "eranian@google.com" Subject: Re: [PATCH 0/3 v2] nmi perf fixes Message-ID: <20100910164224.GA10878@elte.hu> References: <1283454469-1909-1-git-send-email-dzickus@redhat.com> <1284118900.402.35.camel@laptop> <20100910132741.GB4879@redhat.com> <20100910144634.GA1060@elte.hu> <20100910151735.GC13563@erda.amd.com> <1284134283.402.114.camel@laptop> <20100910164129.GD10036@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100910164129.GD10036@elte.hu> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -1.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.0 required=5.9 tests=BAYES_20 autolearn=no SpamAssassin version=3.2.5 -1.0 BAYES_20 BODY: Bayesian spam probability is 5 to 20% [score: 0.0784] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > On Fri, 2010-09-10 at 17:17 +0200, Robert Richter wrote: > > > > perf record -g ./hackbench 10 > > > > > > I try to reproduce it, which systems are affected? > > > > I know for sure Ingo's Barcelona and my Opteron 12xx. > > Havent seen it on an AMD Athlon64 dual-core box - but havent tried > really hard there. Also note that i tried _really_ hard to trigger it on an Intel system (Nehalem), with multi-hour tests, and it didnt trigger there. So this only occurs on AMD systems. Thanks, Ingo