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: <alpine.DEB.2.10.1307250009490.25162@vincent-weaver-1.um.maine.edu>
Date:	Thu, 25 Jul 2013 00:12:45 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Vince Weaver <vincent.weaver@...ne.edu>
cc:	linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
	Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>, mingo@...nel.org,
	acme@...hat.com, Stephane Eranian <eranian@...il.com>
Subject: [PATCH 2/2] Update perf_event ABI documentation: add devices dir
 documentation


There were various perf_event related sysfs entries in the
/sys/bus/event_source/devices/*/ directories that were not
documented.

This is version 2 with fixes suggested by Jiri Olsa.

Acked-by: Jiri Olsa <jolsa@...hat.com>
Signed-off-by: Vince Weaver <vincent.weaver@...ne.edu>

diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices b/Documentation/ABI/testing/sysfs-bus-event_source-devices
new file mode 100644
index 0000000..e7434ee
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices
@@ -0,0 +1,45 @@
+What:		/sys/bus/event_source/devices/<dev>/cpumask
+
+Date:		2012/09/10
+
+Contact:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
+
+Description:	This value holds a representative core for each
+		socket in a system.  It is meant to help when
+		creating a perf_event event for socket-wide events
+		like uncore and northbridge events.
+
+		The format is a comma separated list of cpu numbers,
+		one for each socket in the system that the PMU in
+		question can run on.
+
+		For example, on a two-socket Sandybridge-EP machine and
+		the cbox0 uncore the value of the file will be:
+			0,8
+
+
+What:		/sys/bus/event_source/devices/cpu/rdpmc
+
+Date:		2011/11/20
+
+Contact:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
+
+Description:	Indicates whether a CPU allows userspace "rdpmc"
+		instructions (unprivileged reads of the performance
+		counter MSRs).
+
+		You can echo 0 to this value to disable user rdpmc
+		access.
+
+
+What:		/sys/bus/event_source/devices/<dev>/type
+
+Date:		2013/01/08
+
+Contact:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
+
+Description:	This value holds the PMU (Performance Monitor Unit) type
+		value that is passed into the perf_event_open()
+		attr:type field when opening an event.
+
+		The value is a decimal integer.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ