120 lines · plain
1What: /sys/class/intel_pmt/2Date: October 20203KernelVersion: 5.104Contact: David Box <david.e.box@linux.intel.com>5Description:6 The intel_pmt/ class directory contains information for7 devices that expose hardware telemetry using Intel Platform8 Monitoring Technology (PMT)9 10What: /sys/class/intel_pmt/telem<x>11Date: October 202012KernelVersion: 5.1013Contact: David Box <david.e.box@linux.intel.com>14Description:15 The telem<x> directory contains files describing an instance of16 a PMT telemetry device that exposes hardware telemetry. Each17 telem<x> directory has an associated telem file. This file18 may be opened and mapped or read to access the telemetry space19 of the device. The register layout of the telemetry space is20 determined from an XML file that matches the PCI device id and21 GUID for the device.22 23What: /sys/class/intel_pmt/telem<x>/telem24Date: October 202025KernelVersion: 5.1026Contact: David Box <david.e.box@linux.intel.com>27Description:28 (RO) The telemetry data for this telemetry device. This file29 may be mapped or read to obtain the data.30 31What: /sys/class/intel_pmt/telem<x>/guid32Date: October 202033KernelVersion: 5.1034Contact: David Box <david.e.box@linux.intel.com>35Description:36 (RO) The GUID for this telemetry device. The GUID identifies37 the version of the XML file for the parent device that is to38 be used to get the register layout.39 40What: /sys/class/intel_pmt/telem<x>/size41Date: October 202042KernelVersion: 5.1043Contact: David Box <david.e.box@linux.intel.com>44Description:45 (RO) The size of telemetry region in bytes that corresponds to46 the mapping size for the telem file.47 48What: /sys/class/intel_pmt/telem<x>/offset49Date: October 202050KernelVersion: 5.1051Contact: David Box <david.e.box@linux.intel.com>52Description:53 (RO) The offset of telemetry region in bytes that corresponds to54 the mapping for the telem file.55 56What: /sys/class/intel_pmt/crashlog<x>57Date: October 202058KernelVersion: 5.1059Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>60Description:61 The crashlog<x> directory contains files for configuring an62 instance of a PMT crashlog device that can perform crash data63 recording. Each crashlog<x> device has an associated crashlog64 file. This file can be opened and mapped or read to access the65 resulting crashlog buffer. The register layout for the buffer66 can be determined from an XML file of specified GUID for the67 parent device.68 69What: /sys/class/intel_pmt/crashlog<x>/crashlog70Date: October 202071KernelVersion: 5.1072Contact: David Box <david.e.box@linux.intel.com>73Description:74 (RO) The crashlog buffer for this crashlog device. This file75 may be mapped or read to obtain the data.76 77What: /sys/class/intel_pmt/crashlog<x>/guid78Date: October 202079KernelVersion: 5.1080Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>81Description:82 (RO) The GUID for this crashlog device. The GUID identifies the83 version of the XML file for the parent device that should be84 used to determine the register layout.85 86What: /sys/class/intel_pmt/crashlog<x>/size87Date: October 202088KernelVersion: 5.1089Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>90Description:91 (RO) The length of the result buffer in bytes that corresponds92 to the size for the crashlog buffer.93 94What: /sys/class/intel_pmt/crashlog<x>/offset95Date: October 202096KernelVersion: 5.1097Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>98Description:99 (RO) The offset of the buffer in bytes that corresponds100 to the mapping for the crashlog device.101 102What: /sys/class/intel_pmt/crashlog<x>/enable103Date: October 2020104KernelVersion: 5.10105Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>106Description:107 (RW) Boolean value controlling if the crashlog functionality108 is enabled for the crashlog device.109 110What: /sys/class/intel_pmt/crashlog<x>/trigger111Date: October 2020112KernelVersion: 5.10113Contact: Alexander Duyck <alexander.h.duyck@linux.intel.com>114Description:115 (RW) Boolean value controlling the triggering of the crashlog116 device node. When read it provides data on if the crashlog has117 been triggered. When written to it can be used to either clear118 the current trigger by writing false, or to trigger a new119 event if the trigger is not currently set.120