sysfs-bus-event_source-devices-events 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. What: /sys/devices/cpu/events/
  2. /sys/devices/cpu/events/branch-misses
  3. /sys/devices/cpu/events/cache-references
  4. /sys/devices/cpu/events/cache-misses
  5. /sys/devices/cpu/events/stalled-cycles-frontend
  6. /sys/devices/cpu/events/branch-instructions
  7. /sys/devices/cpu/events/stalled-cycles-backend
  8. /sys/devices/cpu/events/instructions
  9. /sys/devices/cpu/events/cpu-cycles
  10. Date: 2013/01/08
  11. Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
  12. Description: Generic performance monitoring events
  13. A collection of performance monitoring events that may be
  14. supported by many/most CPUs. These events can be monitored
  15. using the 'perf(1)' tool.
  16. The contents of each file would look like:
  17. event=0xNNNN
  18. where 'N' is a hex digit and the number '0xNNNN' shows the
  19. "raw code" for the perf event identified by the file's
  20. "basename".
  21. What: /sys/bus/event_source/devices/<pmu>/events/<event>
  22. Date: 2014/02/24
  23. Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
  24. Description: Per-pmu performance monitoring events specific to the running system
  25. Each file (except for some of those with a '.' in them, '.unit'
  26. and '.scale') in the 'events' directory describes a single
  27. performance monitoring event supported by the <pmu>. The name
  28. of the file is the name of the event.
  29. File contents:
  30. <term>[=<value>][,<term>[=<value>]]...
  31. Where <term> is one of the terms listed under
  32. /sys/bus/event_source/devices/<pmu>/format/ and <value> is
  33. a number is base-16 format with a '0x' prefix (lowercase only).
  34. If a <term> is specified alone (without an assigned value), it
  35. is implied that 0x1 is assigned to that <term>.
  36. Examples (each of these lines would be in a seperate file):
  37. event=0x2abc
  38. event=0x423,inv,cmask=0x3
  39. domain=0x1,offset=0x8,starting_index=0xffff
  40. Each of the assignments indicates a value to be assigned to a
  41. particular set of bits (as defined by the format file
  42. corresponding to the <term>) in the perf_event structure passed
  43. to the perf_open syscall.
  44. What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
  45. Date: 2014/02/24
  46. Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
  47. Description: Perf event units
  48. A string specifying the English plural numerical unit that <event>
  49. (once multiplied by <event>.scale) represents.
  50. Example:
  51. Joules
  52. What: /sys/bus/event_source/devices/<pmu>/events/<event>.scale
  53. Date: 2014/02/24
  54. Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
  55. Description: Perf event scaling factors
  56. A string representing a floating point value expressed in
  57. scientific notation to be multiplied by the event count
  58. recieved from the kernel to match the unit specified in the
  59. <event>.unit file.
  60. Example:
  61. 2.3283064365386962890625e-10
  62. This is provided to avoid performing floating point arithmetic
  63. in the kernel.