Hi, On 12/12/2023 17:55, Randy Dunlap wrote: > Hi-- > > On 12/12/23 11:52, Avadhut Naik wrote: >> ACPI Platform Health Assessment Table (PHAT) enables a platform to expose >> an extensible set of platform health-related telemetry. The telemetry is >> exposed through Firmware Version and Firmware Health Data Records which >> provide version data and health-related information of their associated >> components respectively. >> >> Additionally, the platform also provides Reset Reason Health Record >> in the table highlighting the cause of the last system reset in case >> of expected and unexpected events. Vendor-specific data capturing the >> underlying state of the system during reset can also be optionally >> provided through the record.[1] >> >> Introduce support for parsing, decoding, and logging the PHAT table, if >> supported by the system. By default, the table will be logged to stdout. >> The same, however, can be changed through the "-o" command line parameter. >> Additionally, the tool also provides a hexdump of the entire table, if >> needed, through the "-x" parameter. >> >> Signed-off-by: Avadhut Naik <avadhut.naik@xxxxxxx> >> --- >> Makefile | 12 ++ >> parse_phat.c | 516 +++++++++++++++++++++++++++++++++++++++++++++++++++ >> 2 files changed, 528 insertions(+) >> create mode 100644 Makefile >> create mode 100644 parse_phat.c >> > > Does acpidump not parse the PHAT table? > Could it? Should it? > IIUC, acpidump will only provide a raw hex dump of the entire PHAT table, if present, much like it does for other ACPI tables. The onus is on the user for deciphering the hex dump. I'd think that the parsing functionality can be incorporated in acpidump but not sure if it should be. Would love to head from its maintainers, if possible. > > thanks. -- Thanks, Avadhut Naik
