<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sysfs-class-intel_pmt</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>5ef9998c - platform/x86: Intel PMT Crashlog capability driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-class-intel_pmt#5ef9998c</link>
        <description>platform/x86: Intel PMT Crashlog capability driverAdd support for the Intel Platform Monitoring Technology crashloginterface. This interface provides a few sysfs values to allow forcontrolling the crashlog telemetry interface as well as a characterdriver to allow for mapping the crashlog memory region so that it can beaccessed after a crashlog has been recorded.This driver is meant to only support the server version of the crashlogwhich is identified as crash_type 1 with a version of zero. Currently noother types are supported.Signed-off-by: Alexander Duyck &lt;alexander.h.duyck@linux.intel.com&gt;Signed-off-by: David E. Box &lt;david.e.box@linux.intel.com&gt;Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-class-intel_pmt</description>
        <pubDate>Thu, 29 Oct 2020 01:55:36 +0000</pubDate>
        <dc:creator>Alexander Duyck &lt;alexander.h.duyck@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e2729113 - platform/x86: Intel PMT class driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-class-intel_pmt#e2729113</link>
        <description>platform/x86: Intel PMT class driverIntel Platform Monitoring Technology is meant to provide a common way toaccess telemetry and system metrics.Register mappings are not provided by the driver. Instead, a GUID is readfrom a header for each endpoint. The GUID identifies the device and is tobe used with an XML, provided by the vendor, to discover the available setof metrics and their register mapping.  This allows firmware updates tomodify the register space without needing to update the driver every timewith new mappings. Firmware writes a new GUID in this case to specify thenew mapping.  Software tools with access to the associated XML file canthen interpret the changes.The module manages access to all Intel PMT endpoints on a system,independent of the device exporting them. It creates an intel_pmt classto manage the devices. For each telemetry endpoint, sysfs files provideGUID and size information as well as a pointer to the parent device thetelemetry came from. Software may discover the association betweenendpoints and devices by iterating through the list in sysfs, or by lookingfor the existence of the class folder under the device of interest.  Abinary sysfs attribute of the same name allows software to then read or mapthe telemetry space for direct access.Signed-off-by: Alexander Duyck &lt;alexander.h.duyck@linux.intel.com&gt;Signed-off-by: David E. Box &lt;david.e.box@linux.intel.com&gt;Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-class-intel_pmt</description>
        <pubDate>Thu, 29 Oct 2020 01:55:34 +0000</pubDate>
        <dc:creator>Alexander Duyck &lt;alexander.h.duyck@linux.intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
