linux-kernel - Re: re-enable Nehalem raw Offcore-Events support

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: <20110429164951.GB25491@elte.hu>
Date:	Fri, 29 Apr 2011 18:49:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Vince Weaver <vweaver1@...s.utk.edu>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Stephane Eranian <eranian@...il.com>
Subject: Re: re-enable Nehalem raw Offcore-Events support


* Andi Kleen <ak@...ux.intel.com> wrote:

> On Fri, Apr 29, 2011 at 11:04:46AM -0400, Vince Weaver wrote:
> > Hello Linus
> > 
> > can you revert the commit b52c55c6a25e4515b5e075a989ff346fc251ed09
> 
> Acked-by: Andi Kleen <ak@...ux.intel.com>

I outlined my objections in my reply to Vince.

> (I wrote the original patch)
> 
> > (finally!) added in the 2.6.39 merge window.  However this is a useful 
> > feature and many tools (including the PAPI performance counter library 
> > that I work on) had added support for it in anticipation of the 2.6.39 
> 
> I also use some tools which benefit from this functionality. The extended raw 
> events are very useful to analyze NUMA problems for once.

Mind sharing those methods and help generalizing them and help making them 
useful to non-experts? Peter's patch which adds a 'NUMA' level to the cache 
event abstractions could be a good start.

Only once generalization has been covered sufficiently, once we are sure we can 
stick with the raw ABI, can we push that upstream.

Thanks,

	Ingo
--
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/