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]

Date:	Sun, 1 May 2011 19:55:05 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Corey Ashford <cjashfor@...ux.vnet.ibm.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andi Kleen <ak@...ux.intel.com>,
	Pekka Enberg <penberg@...nel.org>,
	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>,
	Carl Love <carll@...ibm.com>
Subject: Re: re-enable Nehalem raw Offcore-Events support


* Corey Ashford <cjashfor@...ux.vnet.ibm.com> wrote:

> Carl Love and I recently completed some work to add perf_events support for 
> the IBM Blue Waters machine's "CPU networking" chip, called the Torrent chip.  
> We did all of this work based on a RHEL 6 kernel (2.6.32ish), which doesn't 
> have Peter's more recent multi-PMU support.
> 
> I would say that most if not all of the events are not generalizable in the 
> sense that you are talking about; the events are very specific to the Torrent 
> chip. [...]

That's ok and not a problem.

The issue here are events that *are* generalizable.

> So if I'm understanding what you have said correctly, we would not be able to 
> get a forward port of this code committed without abstracting these events in 
> a away that's acceptable to the kernel community. [...]

If the number of events worth generalizing is the empty set that's ok.

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/