linux-kernel - Re: [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore pmu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101210151135.GA7695@lenovo>
Date:	Fri, 10 Dec 2010 18:11:35 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Stephane Eranian <eranian@...gle.com>,
	Lin Ming <ming.m.lin@...el.com>,
	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore pmu

On Fri, Dec 10, 2010 at 11:52:15AM +0100, Peter Zijlstra wrote:
> On Fri, 2010-12-10 at 11:47 +0100, Peter Zijlstra wrote:
> > On Fri, 2010-12-10 at 00:46 +0100, Stephane Eranian wrote:
> > > Hi,
> > > 
> > > So I have tested this patch a bit on WSM and as I expected there
> > > are issues with sampling.
> > > 
> > > When HT is on, both siblings CPUs get the interrupt. The HW does not
> > > allow you to only point interrupts to a single HT thread (CPU).
> > 
> > Egads, how ugly :/
> >

crap...
...
 
> 
> That would of course need to also grow some smarts to detect if there is
> only 1 sibling online.
> 
> CC'ed Cyrill as P4 might have something similar.
> 

Yes, Don was testing p4 stuff for me and have reported this issue as well.
I'll check what I can do. Thanks for CC'ing me.

  Cyrill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/