linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	mingo@kernel.org, acme@redhat.com,
	Stephane Eranian <eranian@gmail.com>
Subject: Re: perf documentation: update Documentation/ABI/testing with missing perf-related files
Date: Tue, 16 Jul 2013 10:35:49 +0200	[thread overview]
Message-ID: <20130716083549.GC1098@krava.brq.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1307151736250.6555@vincent-weaver-1.um.maine.edu>

On Mon, Jul 15, 2013 at 05:38:15PM -0400, Vince Weaver wrote:
> 
> Add documentation for various files perf_event creates under
> /sys/bus/event_source/devices/<dev>/
> 
> Signed-off-by: Vince Weaver <vincent.weaver@maine.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..ffa2e4b
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices
> @@ -0,0 +1,50 @@
> +What:		/sys/bus/event_source/devices/<dev>/cpumask
> +
> +Date:		2012/09/10
> +		

nit, white space above

> +Contact:	Linux kernel mailing list <linux-kernel@vger.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
> +		    

nit, white space above

> +
> +
> +What:		/sys/bus/event_source/devices/cpu/rdpmc
> +
> +Date:		2011/11/20
> +
> +Contact:	Linux kernel mailing list <linux-kernel@vger.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@vger.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.
> +
> +
> +

Acked-by: Jiri Olsa <jolsa@redhat.com>

thanks,
jirka

      reply	other threads:[~2013-07-16  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 21:38 perf documentation: update Documentation/ABI/testing with missing perf-related files Vince Weaver
2013-07-16  8:35 ` Jiri Olsa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130716083549.GC1098@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vincent.weaver@maine.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).