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  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:	Sat, 30 Jan 2010 09:42:59 +0100
From:	Peter Zijlstra <>
To:	Corey Ashford <>
Cc:	Ingo Molnar <>, LKML <>,
	Andi Kleen <>,
	Paul Mackerras <>,
	Stephane Eranian <>,
	Frederic Weisbecker <>,
	Xiao Guangrong <>,
	Dan Terpstra <>,
	Philip Mucci <>,
	Maynard Johnson <>,
	Carl Love <>,
	Steven Rostedt <>,
	Arnaldo Carvalho de Melo <>,
	Masami Hiramatsu <>
Subject: Re: [RFC] perf_events: support for uncore a.k.a. nest units

On Fri, 2010-01-29 at 15:05 -0800, Corey Ashford wrote:
> So you'd read the id from the sysfs topology tree, and then pass that id to the 
> interface?  That's an interesting approach that eliminates the need to pass a 
> string pmu path to the kernel. 

No, the attr.pmu_id would reflect the location in the tree (pci
location, or spu number), the pmu id reported would identify the kind of
pmu driver used for that particular device.

I realized this confusion after sending but didn't clarify, we should
come up with a good alternative name for either (or both) uses.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists