sysfs-bus-event_source-devices-hv_24x7 1.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog
  2. Date: February 2014
  3. Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
  4. Description:
  5. Provides access to the binary "24x7 catalog" provided by the
  6. hypervisor on POWER7 and 8 systems. This catalog lists events
  7. avaliable from the powerpc "hv_24x7" pmu. Its format is
  8. documented here:
  9. https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h
  10. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length
  11. Date: February 2014
  12. Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
  13. Description:
  14. A number equal to the length in bytes of the catalog. This is
  15. also extractable from the provided binary "catalog" sysfs entry.
  16. What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version
  17. Date: February 2014
  18. Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
  19. Description:
  20. Exposes the "version" field of the 24x7 catalog. This is also
  21. extractable from the provided binary "catalog" sysfs entry.
  22. What: /sys/bus/event_source/devices/hv_24x7/event_descs/<event-name>
  23. Date: February 2014
  24. Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
  25. Description:
  26. Provides the description of a particular event as provided by
  27. the firmware. If firmware does not provide a description, no
  28. file will be created.
  29. Note that the event-name lacks the domain suffix appended for
  30. events in the events/ dir.
  31. What: /sys/bus/event_source/devices/hv_24x7/event_long_descs/<event-name>
  32. Date: February 2014
  33. Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
  34. Description:
  35. Provides the "long" description of a particular event as
  36. provided by the firmware. If firmware does not provide a
  37. description, no file will be created.
  38. Note that the event-name lacks the domain suffix appended for
  39. events in the events/ dir.