sysfs-bus-event_source-devices-hv_24x7 3.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. What: /sys/bus/event_source/devices/hv_24x7/format
  2. Date: September 2020
  3. Contact: Linux on PowerPC Developer List <[email protected]>
  4. Description: Read-only. Attribute group to describe the magic bits
  5. that go into perf_event_attr.config for a particular pmu.
  6. (See ABI/testing/sysfs-bus-event_source-devices-format).
  7. Each attribute under this group defines a bit range of the
  8. perf_event_attr.config. All supported attributes are listed
  9. below::
  10. chip = "config:16-31"
  11. core = "config:16-31"
  12. domain = "config:0-3"
  13. lpar = "config:0-15"
  14. offset = "config:32-63"
  15. vcpu = "config:16-31"
  16. For example::
  17. PM_PB_CYC = "domain=1,offset=0x80,chip=?,lpar=0x0"
  18. In this event, '?' after chip specifies that
  19. this value will be provided by user while running this event.
  20. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog
  21. Date: February 2014
  22. Contact: Linux on PowerPC Developer List <[email protected]>
  23. Description:
  24. Provides access to the binary "24x7 catalog" provided by the
  25. hypervisor on POWER7 and 8 systems. This catalog lists events
  26. available from the powerpc "hv_24x7" pmu. Its format is
  27. documented here:
  28. https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h
  29. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length
  30. Date: February 2014
  31. Contact: Linux on PowerPC Developer List <[email protected]>
  32. Description:
  33. A number equal to the length in bytes of the catalog. This is
  34. also extractable from the provided binary "catalog" sysfs entry.
  35. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version
  36. Date: February 2014
  37. Contact: Linux on PowerPC Developer List <[email protected]>
  38. Description:
  39. Exposes the "version" field of the 24x7 catalog. This is also
  40. extractable from the provided binary "catalog" sysfs entry.
  41. What: /sys/devices/hv_24x7/interface/sockets
  42. Date: May 2020
  43. Contact: Linux on PowerPC Developer List <[email protected]>
  44. Description: read only
  45. This sysfs interface exposes the number of sockets present in the
  46. system.
  47. What: /sys/devices/hv_24x7/interface/chipspersocket
  48. Date: May 2020
  49. Contact: Linux on PowerPC Developer List <[email protected]>
  50. Description: read only
  51. This sysfs interface exposes the number of chips per socket
  52. present in the system.
  53. What: /sys/devices/hv_24x7/interface/coresperchip
  54. Date: May 2020
  55. Contact: Linux on PowerPC Developer List <[email protected]>
  56. Description: read only
  57. This sysfs interface exposes the number of cores per chip
  58. present in the system.
  59. What: /sys/devices/hv_24x7/cpumask
  60. Date: July 2020
  61. Contact: Linux on PowerPC Developer List <[email protected]>
  62. Description: read only
  63. This sysfs file exposes the cpumask which is designated to make
  64. HCALLs to retrieve hv-24x7 pmu event counter data.
  65. What: /sys/bus/event_source/devices/hv_24x7/event_descs/<event-name>
  66. Date: February 2014
  67. Contact: Linux on PowerPC Developer List <[email protected]>
  68. Description:
  69. Provides the description of a particular event as provided by
  70. the firmware. If firmware does not provide a description, no
  71. file will be created.
  72. Note that the event-name lacks the domain suffix appended for
  73. events in the events/ dir.
  74. What: /sys/bus/event_source/devices/hv_24x7/event_long_descs/<event-name>
  75. Date: February 2014
  76. Contact: Linux on PowerPC Developer List <[email protected]>
  77. Description:
  78. Provides the "long" description of a particular event as
  79. provided by the firmware. If firmware does not provide a
  80. description, no file will be created.
  81. Note that the event-name lacks the domain suffix appended for
  82. events in the events/ dir.