From: "Mario Limonciello (AMD)" <superm1@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>,
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
Jean Delvare <jdelvare@suse.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
"Mario Limonciello (AMD)" <superm1@kernel.org>
Subject: [PATCH v2 0/7] Parse SMBIOS additional entries
Date: Tue, 16 Dec 2025 06:33:47 -0600 [thread overview]
Message-ID: <20251216123354.9219-1-superm1@kernel.org> (raw)
The SMBIOS additional entries on AMD Zen4+ systems running an AGESA
based BIOS contain information about the AGESA version which can be
useful for matching the software stack when debugging an issue.
Add support for parsing this from SMBIOS tables and output it into
the logs at bootup. Additionally export the information to debugfs
in case users are interested in any other strings.
v2:
* Move message to arch/x86/kernel/cpu/amd.c
* Optimizations for LKP robot reported comments
* Add tags
* Add other (unused) missing enums that match spec
Mario Limonciello (AMD) (7):
firmware: dmi: Correct an indexing error in dmi.h
firmware: dmi: Adjust dmi_decode() to use enums
firmware: dmi: Read additional information when decoding DMI table
firmware: dmi: Add debugfs for additional information entries
firmware: dmi: Add missing DMI entry types
x86/CPU/AMD: Prefix messages with x86/amd
x86/CPU/AMD: Output the AGESA version to the logs
arch/x86/kernel/cpu/amd.c | 22 ++++++++-
drivers/firmware/dmi_scan.c | 92 ++++++++++++++++++++++++++++++++-----
include/linux/dmi.h | 12 +++++
3 files changed, 114 insertions(+), 12 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-16 12:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 12:33 Mario Limonciello (AMD) [this message]
2025-12-16 12:33 ` [PATCH v2 1/7] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2025-12-22 16:48 ` Jean Delvare
2025-12-16 12:33 ` [PATCH v2 2/7] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2025-12-22 16:50 ` Jean Delvare
2025-12-16 12:33 ` [PATCH v2 3/7] firmware: dmi: Read additional information when decoding DMI table Mario Limonciello (AMD)
2025-12-17 21:03 ` Yazen Ghannam
2025-12-17 21:09 ` Mario Limonciello
2025-12-17 21:21 ` Yazen Ghannam
2025-12-17 21:23 ` Mario Limonciello
2025-12-18 15:43 ` Yazen Ghannam
2025-12-22 16:59 ` Jean Delvare
2025-12-22 17:51 ` Jean Delvare
2025-12-22 21:31 ` Jean DELVARE
2025-12-16 12:33 ` [PATCH v2 4/7] firmware: dmi: Add debugfs for additional information entries Mario Limonciello (AMD)
2025-12-16 12:33 ` [PATCH v2 5/7] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2025-12-22 17:01 ` Jean Delvare
2025-12-16 12:33 ` [PATCH v2 6/7] x86/CPU/AMD: Prefix messages with x86/amd Mario Limonciello (AMD)
2025-12-17 21:10 ` Yazen Ghannam
2025-12-16 12:33 ` [PATCH v2 7/7] x86/CPU/AMD: Output the AGESA version to the logs Mario Limonciello (AMD)
2025-12-17 21:18 ` Yazen Ghannam
2025-12-17 21:21 ` Mario Limonciello
2025-12-18 15:47 ` Yazen Ghannam
2025-12-22 18:18 ` Jean Delvare
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=20251216123354.9219-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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