![]() We only had to pile everything into the src/fuzzing/firmware directory because honggfuzz could not cope with more than one input path. This way each plugin is self contained and easy to copy. Also, install the fuzzing builder objects as this fixes the installed tests when srcdir does not exist. Based on a patch by Jan Tojnar <jtojnar@gmail.com>, many thanks. |
||
---|---|---|
.. | ||
tests | ||
fu-acpi-phat-health-record.c | ||
fu-acpi-phat-health-record.h | ||
fu-acpi-phat-version-element.c | ||
fu-acpi-phat-version-element.h | ||
fu-acpi-phat-version-record.c | ||
fu-acpi-phat-version-record.h | ||
fu-acpi-phat.c | ||
fu-acpi-phat.h | ||
fu-plugin-acpi-phat.c | ||
fu-self-test.c | ||
meson.build | ||
README.md |
Platform Health Assessment Table
Introduction
The PHAT is an ACPI table where a platform can expose health related telemetry that may be useful for software running within the constraints of an OS.
These elements are typically going to encompass things that are likely otherwise not enumerable during the OS runtime phase of operations, such as version of pre-OS components.
The daemon includes some of the PHAT data in the report data sent to the LVFS so that we can debug failures with the help of the IHV. This allows us to find the root cause of the problem, and so we know what other OEMs may be affected.
See https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/05_ACPI_Software_Programming_Model/ACPI_Software_Programming_Model.html#platform-health-assessment-table for more information.
External Interface Access
This plugin requires read access to /sys/firmware/acpi/tables
.