Listing specific events doesn't actually help us at all here because:
 - these events actually vary between different ppc processors, they
   aren't garunteed to be present.
 - the documentation of the file contents is now duplicated by the
   docs for arbitrary event file contents.

Signed-off-by: Cody P Schafer <c...@linux.vnet.ibm.com>
---
 .../testing/sysfs-bus-event_source-devices-events  | 57 ----------------------
 1 file changed, 57 deletions(-)

diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events 
b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
index 5393e1ed6..50c30a6 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-events
@@ -26,63 +26,6 @@ Description: Generic performance monitoring events
                "raw code" for the perf event identified by the file's
                "basename".
 
-
-What:          /sys/devices/cpu/events/PM_1PLUS_PPC_CMPL
-               /sys/devices/cpu/events/PM_BRU_FIN
-               /sys/devices/cpu/events/PM_BR_MPRED
-               /sys/devices/cpu/events/PM_CMPLU_STALL
-               /sys/devices/cpu/events/PM_CMPLU_STALL_BRU
-               /sys/devices/cpu/events/PM_CMPLU_STALL_DCACHE_MISS
-               /sys/devices/cpu/events/PM_CMPLU_STALL_DFU
-               /sys/devices/cpu/events/PM_CMPLU_STALL_DIV
-               /sys/devices/cpu/events/PM_CMPLU_STALL_ERAT_MISS
-               /sys/devices/cpu/events/PM_CMPLU_STALL_FXU
-               /sys/devices/cpu/events/PM_CMPLU_STALL_IFU
-               /sys/devices/cpu/events/PM_CMPLU_STALL_LSU
-               /sys/devices/cpu/events/PM_CMPLU_STALL_REJECT
-               /sys/devices/cpu/events/PM_CMPLU_STALL_SCALAR
-               /sys/devices/cpu/events/PM_CMPLU_STALL_SCALAR_LONG
-               /sys/devices/cpu/events/PM_CMPLU_STALL_STORE
-               /sys/devices/cpu/events/PM_CMPLU_STALL_THRD
-               /sys/devices/cpu/events/PM_CMPLU_STALL_VECTOR
-               /sys/devices/cpu/events/PM_CMPLU_STALL_VECTOR_LONG
-               /sys/devices/cpu/events/PM_CYC
-               /sys/devices/cpu/events/PM_GCT_NOSLOT_BR_MPRED
-               /sys/devices/cpu/events/PM_GCT_NOSLOT_BR_MPRED_IC_MISS
-               /sys/devices/cpu/events/PM_GCT_NOSLOT_CYC
-               /sys/devices/cpu/events/PM_GCT_NOSLOT_IC_MISS
-               /sys/devices/cpu/events/PM_GRP_CMPL
-               /sys/devices/cpu/events/PM_INST_CMPL
-               /sys/devices/cpu/events/PM_LD_MISS_L1
-               /sys/devices/cpu/events/PM_LD_REF_L1
-               /sys/devices/cpu/events/PM_RUN_CYC
-               /sys/devices/cpu/events/PM_RUN_INST_CMPL
-
-Date:          2013/01/08
-
-Contact:       Linux kernel mailing list <linux-ker...@vger.kernel.org>
-               Linux Powerpc mailing list <linuxppc-...@ozlabs.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.
-
 What: /sys/bus/event_source/devices/<pmu>/events/<event>
 Date: 2014/02/24
 Contact:       Linux kernel mailing list <linux-ker...@vger.kernel.org>
-- 
1.9.0

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to