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]

Message-ID: <1273571322.5605.3523.camel@twins>
Date:	Tue, 11 May 2010 11:48:42 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"eranian@...il.com" <eranian@...il.com>,
	"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
	"arjan@...ux.intel.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>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Will Deacon <will.deacon@....com>,
	Maynard Johnson <mpjohn@...ibm.com>,
	Carl Love <carll@...ibm.com>,
	"greg@...ah.com" <greg@...ah.com>,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: [RFC][PATCH 3/9] perf: export registerred pmus via sysfs

On Tue, 2010-05-11 at 17:40 +0800, Lin Ming wrote:
> /sys/devices/system/cpu/cpu0/cpu_hw_events/*
> /sys/devices/system/cpu/cpu0/cpu_hw_cache_events/*
> /sys/devices/system/cpu/cpu0/cpu_raw_events/*
> ....
> ....
> /sys/devices/system/cpu/cpuN/cpu_hw_events/*
> /sys/devices/system/cpu/cpuN/cpu_hw_cache_events/*
> /sys/devices/system/cpu/cpuN/cpu_raw_events/*
> 
> Is /sys/class/event_sources/* looks like,
> 
> /sys/class/event_sources/cpu_hw_events0
> -> /sys/devices/system/cpu/cpu0/cpu_hw_events
> ...
> /sys/class/event_sources/cpu_hw_eventsN
> -> /sys/devices/system/cpu/cpuN/cpu_hw_events
> 
> /sys/class/event_sources/cpu_hw_cache_events0
> -> /sys/devices/system/cpu/cpu0/cpu_hw_events
> ...
> /sys/class/event_sources/cpu_hw_cache_eventsN
> -> /sys/devices/system/cpu/cpuN/cpu_hw_events

Hmm, good question.

No all the cpus would have the same event sources. I'm not sure if we
can make sysfs understand that though (added GregKH and Kay to CC).

Possibly we'd have to place them at the cpu level, like:

 /sys/devices/system/cpu/cpu_*_events/

and have links like:

 /sys/devices/system/cpu/cpuN/cpu_*_events ->
    /sys/devices/system/cpu/cpu_*_events/

as well as

 /sys/class/event_sources/cpu_*_events ->
    /sys/devices/system/cpu/cpu_*_events/


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