[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130122171013.GM1037@krava.brq.redhat.com>
Date: Tue, 22 Jan 2013 18:10:13 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Anton Blanchard <anton@....ibm.com>, robert.richter@....com,
linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <ak@...ux.intel.com>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries
On Fri, Jan 18, 2013 at 09:46:54AM -0800, Sukadev Bhattiprolu wrote:
> Jiri Olsa [jolsa@...hat.com] wrote:
SNIP
> +
> +Contact: Linux kernel mailing list <linux-kernel@...r.kernel.org>
> + Linux Powerpc mailing list <linuxppc-dev@...abs.org>
> +
> +Description: POWER-systems specific performance monitoring events
> +
> + A collection of performance monitoring events that may be
> + supported by the POWER CPU. These events can be monitored
> + using the 'perf(1)' tool.
> +
> + These events may not be supported by other CPUs.
> +
> + The contents of each file would look like:
> +
> + event=0xNNNN
> +
> + where 'N' is a hex digit and the number '0xNNNN' shows the
> + "raw code" for the perf event identified by the file's
> + "basename".
> +
> + Further, multiple terms like 'event=0xNNNN' can be specified
> + and separated with comma. All available terms are defined in
> + the /sys/bus/event_source/devices/<dev>/format file.
Acked-by: Jiri Olsa <jolsa@...hat.com>
thanks,
jirka
--
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