Re: [PATCH V15 00/19] perf, tools: Add support for PMU events in JSON format

[Sukadev Bhattiprolu]

Sukadev Bhattiprolu [sukadev@xxxxxxxxxxxxxxxxxx] wrote:
| CPUs support a large number of performance monitoring events (PMU events)
| and often these events are very specific to an architecture/model of the
| CPU. To use most of these PMU events with perf, we currently have to identify
| them by their raw codes:
| 
| 	perf stat -e r100f2 sleep 1
| 
| This patchset allows architectures to specify these PMU events in JSON
| files located in 'tools/perf/pmu-events/arch/' of the mainline tree.
| The events from the JSON files for the architecture are then built into
| the perf binary.
| 
| At run time, perf identifies the specific set of events for the CPU and
| creates "event aliases". These aliases allow users to specify events by
| "name" as:
| 
| 	perf stat -e pm_1plus_ppc_cmpl sleep 1
| 
| The file, 'tools/perf/pmu-events/README' in [PATCH 19/19] gives more
| details.
| 
| Note:
| 	- All known events tables for the architecture are included in the
| 	  perf binary.
| 
| 	- For architectures that don't have any JSON files, an empty mapping
| 	  table is created and they should continue to build)
| 
| Thanks to input from Andi Kleen, Jiri Olsa, Namhyung Kim and Ingo Molnar.
| 
| These patches are available from:
| 
| 	https://github.com:sukadev/linux.git 
| 	
| 	Branch			Description
| 	------------------------------------------------------
| 	json-v15		Source Code only 
| 	json-files-5		x86 and Powerpc datafiles only
| 	json-v15-with-data	Both code and data (build/test)
| 	
| NOTE: 	Only "source code" patches (i.e those in json-v15) are being emailed.
| 	Please pull the "data files" from the json-files-5 branch.

Ingo, Arnaldo,

Any updates on this patchset? They have been reviewed/acked by Jiri
and we have not received any comments since then.

Is there a chance this can make it into 4.3?

Sukadev

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/