linux-kernel - Re: [RFC][PATCH 3/9] perf: export registerred pmus via sysfs

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:	Tue, 11 May 2010 08:34:54 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Will Deacon <will.deacon@....com>
Cc:	Lin Ming <ming.m.lin@...el.com>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>, eranian@...il.com,
	"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	arjan@...ux.intel.com,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Paul Mackerras <paulus@...ba.org>,
	"David S. Miller" <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Paul Mundt <lethal@...ux-sh.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 3/9] perf: export registerred pmus via sysfs

On Mon, 2010-05-10 at 21:25 +0100, Will Deacon wrote:
> Another interesting ARM-ism is the vast potential for uncore event
> sources in SoC devices. The `node' terminology seems a bit confusing
> here, as there may be counters situated at various points of a bus
> hierarchy which monitor various types of transactions for example. I
> suppose these could live under /sys/devices/system/bus/... ?

Right there are more such systems, and yes hooking them into the
appropriate machine topology like PCI busses is exactly the intent.

I already mentioned the GPU PMUs living in the appropriate PCI device.
But yes, there are far more exotic configurations out there.

>  I would
> expect these kind of counters to be controlled via raw events because
> having a list of discrete events doesn't really make sense [for example,
> if I want to count all bursts of a given size, I can encode the burst
> size into the event number]. 

Raw is fine, its only once these things start to converge and show
common traits that adding a 'generic' event class becomes useful, and
this is something that can always be done later.
--
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/