1e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/ 2e2729113SAlexander DuyckDate: October 2020 3e2729113SAlexander DuyckKernelVersion: 5.10 4e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 5e2729113SAlexander DuyckDescription: 6e2729113SAlexander Duyck The intel_pmt/ class directory contains information for 7e2729113SAlexander Duyck devices that expose hardware telemetry using Intel Platform 8e2729113SAlexander Duyck Monitoring Technology (PMT) 9e2729113SAlexander Duyck 10e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/telem<x> 11e2729113SAlexander DuyckDate: October 2020 12e2729113SAlexander DuyckKernelVersion: 5.10 13e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 14e2729113SAlexander DuyckDescription: 15e2729113SAlexander Duyck The telem<x> directory contains files describing an instance of 16e2729113SAlexander Duyck a PMT telemetry device that exposes hardware telemetry. Each 17e2729113SAlexander Duyck telem<x> directory has an associated telem file. This file 18e2729113SAlexander Duyck may be opened and mapped or read to access the telemetry space 19e2729113SAlexander Duyck of the device. The register layout of the telemetry space is 20e2729113SAlexander Duyck determined from an XML file that matches the PCI device id and 21e2729113SAlexander Duyck GUID for the device. 22e2729113SAlexander Duyck 23e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/telem<x>/telem 24e2729113SAlexander DuyckDate: October 2020 25e2729113SAlexander DuyckKernelVersion: 5.10 26e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 27e2729113SAlexander DuyckDescription: 28e2729113SAlexander Duyck (RO) The telemetry data for this telemetry device. This file 29e2729113SAlexander Duyck may be mapped or read to obtain the data. 30e2729113SAlexander Duyck 31e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/telem<x>/guid 32e2729113SAlexander DuyckDate: October 2020 33e2729113SAlexander DuyckKernelVersion: 5.10 34e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 35e2729113SAlexander DuyckDescription: 36e2729113SAlexander Duyck (RO) The GUID for this telemetry device. The GUID identifies 37e2729113SAlexander Duyck the version of the XML file for the parent device that is to 38e2729113SAlexander Duyck be used to get the register layout. 39e2729113SAlexander Duyck 40e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/telem<x>/size 41e2729113SAlexander DuyckDate: October 2020 42e2729113SAlexander DuyckKernelVersion: 5.10 43e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 44e2729113SAlexander DuyckDescription: 45e2729113SAlexander Duyck (RO) The size of telemetry region in bytes that corresponds to 46e2729113SAlexander Duyck the mapping size for the telem file. 47e2729113SAlexander Duyck 48e2729113SAlexander DuyckWhat: /sys/class/intel_pmt/telem<x>/offset 49e2729113SAlexander DuyckDate: October 2020 50e2729113SAlexander DuyckKernelVersion: 5.10 51e2729113SAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 52e2729113SAlexander DuyckDescription: 53e2729113SAlexander Duyck (RO) The offset of telemetry region in bytes that corresponds to 54e2729113SAlexander Duyck the mapping for the telem file. 55*5ef9998cSAlexander Duyck 56*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x> 57*5ef9998cSAlexander DuyckDate: October 2020 58*5ef9998cSAlexander DuyckKernelVersion: 5.10 59*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 60*5ef9998cSAlexander DuyckDescription: 61*5ef9998cSAlexander Duyck The crashlog<x> directory contains files for configuring an 62*5ef9998cSAlexander Duyck instance of a PMT crashlog device that can perform crash data 63*5ef9998cSAlexander Duyck recording. Each crashlog<x> device has an associated crashlog 64*5ef9998cSAlexander Duyck file. This file can be opened and mapped or read to access the 65*5ef9998cSAlexander Duyck resulting crashlog buffer. The register layout for the buffer 66*5ef9998cSAlexander Duyck can be determined from an XML file of specified GUID for the 67*5ef9998cSAlexander Duyck parent device. 68*5ef9998cSAlexander Duyck 69*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/crashlog 70*5ef9998cSAlexander DuyckDate: October 2020 71*5ef9998cSAlexander DuyckKernelVersion: 5.10 72*5ef9998cSAlexander DuyckContact: David Box <david.e.box@linux.intel.com> 73*5ef9998cSAlexander DuyckDescription: 74*5ef9998cSAlexander Duyck (RO) The crashlog buffer for this crashlog device. This file 75*5ef9998cSAlexander Duyck may be mapped or read to obtain the data. 76*5ef9998cSAlexander Duyck 77*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/guid 78*5ef9998cSAlexander DuyckDate: October 2020 79*5ef9998cSAlexander DuyckKernelVersion: 5.10 80*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 81*5ef9998cSAlexander DuyckDescription: 82*5ef9998cSAlexander Duyck (RO) The GUID for this crashlog device. The GUID identifies the 83*5ef9998cSAlexander Duyck version of the XML file for the parent device that should be 84*5ef9998cSAlexander Duyck used to determine the register layout. 85*5ef9998cSAlexander Duyck 86*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/size 87*5ef9998cSAlexander DuyckDate: October 2020 88*5ef9998cSAlexander DuyckKernelVersion: 5.10 89*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 90*5ef9998cSAlexander DuyckDescription: 91*5ef9998cSAlexander Duyck (RO) The length of the result buffer in bytes that corresponds 92*5ef9998cSAlexander Duyck to the size for the crashlog buffer. 93*5ef9998cSAlexander Duyck 94*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/offset 95*5ef9998cSAlexander DuyckDate: October 2020 96*5ef9998cSAlexander DuyckKernelVersion: 5.10 97*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 98*5ef9998cSAlexander DuyckDescription: 99*5ef9998cSAlexander Duyck (RO) The offset of the buffer in bytes that corresponds 100*5ef9998cSAlexander Duyck to the mapping for the crashlog device. 101*5ef9998cSAlexander Duyck 102*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/enable 103*5ef9998cSAlexander DuyckDate: October 2020 104*5ef9998cSAlexander DuyckKernelVersion: 5.10 105*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 106*5ef9998cSAlexander DuyckDescription: 107*5ef9998cSAlexander Duyck (RW) Boolean value controlling if the crashlog functionality 108*5ef9998cSAlexander Duyck is enabled for the crashlog device. 109*5ef9998cSAlexander Duyck 110*5ef9998cSAlexander DuyckWhat: /sys/class/intel_pmt/crashlog<x>/trigger 111*5ef9998cSAlexander DuyckDate: October 2020 112*5ef9998cSAlexander DuyckKernelVersion: 5.10 113*5ef9998cSAlexander DuyckContact: Alexander Duyck <alexander.h.duyck@linux.intel.com> 114*5ef9998cSAlexander DuyckDescription: 115*5ef9998cSAlexander Duyck (RW) Boolean value controlling the triggering of the crashlog 116*5ef9998cSAlexander Duyck device node. When read it provides data on if the crashlog has 117*5ef9998cSAlexander Duyck been triggered. When written to it can be used to either clear 118*5ef9998cSAlexander Duyck the current trigger by writing false, or to trigger a new 119*5ef9998cSAlexander Duyck event if the trigger is not currently set. 120