From: Avadhut Naik <avadhut.naik@amd.com>
To: <linux-acpi@vger.kernel.org>, <linux-edac@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <yazen.ghannam@amd.com>,
<avadnaik@amd.com>
Subject: [PATCH 0/1] Tool for parsing the ACPI PHAT Table
Date: Tue, 12 Dec 2023 13:52:18 -0600 [thread overview]
Message-ID: <20231212195219.2348858-1-avadhut.naik@amd.com> (raw)
Hi,
Future AMD SOCs will support the ACPI Platform Health Assessment Table
(PHAT) to export an extensible set of platform health related telemetry
through Firmware Version and Firmware Health Data Records.
The table will also export the Reset Reason Health Record which highlights
the cause of the last system reset in case of both expected and unexpected
events. Vendor-specific data capturing the underlying state of the system
during reset will also be exported through the record.
As such, the table, in general, provides important debugging information,
supplementing the existing error reporting mechanisms on the platform viz.
BERT, CPER, etc., especially when debugging unexpected resets.[1]
With that end in view, we developed this tool for parsing the PHAT table
on SOCs that support it. However, we were somewhat confused about existing,
appropriate projects through which this tool can be shared.
Any recommendations on / pointers to projects through which this tool can be
shared with end users? Will personally work with the project maintainers to
have this tool incorporated there.
TIA!
[1] ACPI specification 6.5, section 5.2.31.5
Avadhut Naik (1):
parse_phat: Add support for ACPI PHAT Table parsing
--
2.34.1
next reply other threads:[~2023-12-12 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 19:52 Avadhut Naik [this message]
2023-12-12 19:52 ` [PATCH 1/1] parse_phat: Add support for ACPI PHAT Table parsing Avadhut Naik
2023-12-12 23:55 ` Randy Dunlap
2023-12-13 0:48 ` Avadhut Naik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231212195219.2348858-1-avadhut.naik@amd.com \
--to=avadhut.naik@amd.com \
--cc=avadnaik@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yazen.ghannam@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®