From: Jean Delvare <jdelvare@suse.de>
To: "Mario Limonciello (AMD)" <superm1@kernel.org>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v6 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry
Date: Wed, 1 Apr 2026 11:17:01 +0200 [thread overview]
Message-ID: <20260401111701.536cfda1@endymion> (raw)
In-Reply-To: <20260307141024.819807-6-superm1@kernel.org>
On Sat, 7 Mar 2026 08:10:24 -0600, Mario Limonciello (AMD) wrote:
> From: Yazen Ghannam <yazen.ghannam@amd.com>
>
> Type 40 entries (Additional Information) are summarized in section 7.41
> as part of the SMBIOS specification. Generally, these entries aren't
> interesting to save.
>
> However on some AMD Zen systems, the AGESA version is stored here. This
> is useful to save to the kernel message logs for debugging. It can be
> used to cross-reference issues.
>
> Implement an iterator for the Additional Information entries. Use this
> to find and print the AGESA string. Do so in AMD code, since the use
> case is AMD-specific.
>
> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
> Co-developed-by: "Mario Limonciello (AMD)" <superm1@kernel.org>
> Signed-off-by: "Mario Limonciello (AMD)" <superm1@kernel.org>
Looks good to me.
Reviewed-by: Jean Delvare <jdelvare@suse.de>
I only have one question:
> (...)
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> (...)
> +static void __init dmi_scan_additional(const struct dmi_header *d, void *p)
> +{
> + struct dmi_a_info *info = (struct dmi_a_info *)d;
> + void *next, *end;
> +
> + if (!IS_ENABLED(CONFIG_DMI))
> + return;
> +
> + if (info->header.type != DMI_ENTRY_ADDITIONAL ||
> + info->header.length < DMI_A_INFO_MIN_SIZE ||
> + info->count < 1)
> + return;
> +
> + next = (void *)(info + 1);
> + end = (void *)info + info->header.length;
> +
> + do {
> + struct dmi_a_info_entry *entry;
> + const char *string_ptr;
> +
> + entry = (struct dmi_a_info_entry *)next;
> +
> + /*
> + * Not much can be done to validate data. At least the entry
> + * length shouldn't be 0.
> + */
> + if (!entry->length)
> + return;
> +
> + string_ptr = dmi_string_nosave(&info->header, entry->str_num);
> +
> + /* Sample string: AGESA!V9 StrixKrackanPI-FP8 1.1.0.0c */
> + if (!strncmp(string_ptr, "AGESA!V9", 8) && strlen(string_ptr) > 9) {
Isn't "V9" going to become "V10" at some point in the future, and then
the AGESA string will no longer be displayed until the code is
adjusted? Or will AMD move the information to a more appropriate place
by then?
Also, I know this was discussed before, but the current print strategy
omits "V9". Is this not something we are going to regret once more
versions are available and we may have to differentiate between them?
> + pr_info("AGESA: %s\n", string_ptr + 9);
> + break;
> + }
> +
> + next += entry->length;
> + } while (end - next >= DMI_A_INFO_ENT_MIN_SIZE);
> +}
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2026-04-01 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 14:10 [PATCH v6 0/5] Print AGESA version at bootup Mario Limonciello (AMD)
2026-03-07 14:10 ` [PATCH v6 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-04-01 19:34 ` [tip: x86/platform] " tip-bot2 for Mario Limonciello (AMD)
2026-03-07 14:10 ` [PATCH v6 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-04-01 19:34 ` [tip: x86/platform] " tip-bot2 for Mario Limonciello (AMD)
2026-03-07 14:10 ` [PATCH v6 3/5] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-04-01 11:03 ` Borislav Petkov
2026-04-01 13:16 ` Mario Limonciello (AMD)
2026-04-01 18:49 ` Borislav Petkov
2026-03-07 14:10 ` [PATCH v6 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-04-01 19:34 ` [tip: x86/platform] " tip-bot2 for Mario Limonciello (AMD)
2026-03-07 14:10 ` [PATCH v6 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry Mario Limonciello (AMD)
2026-04-01 9:17 ` Jean Delvare [this message]
2026-04-01 10:29 ` Borislav Petkov
2026-04-01 11:45 ` Borislav Petkov
2026-04-01 13:14 ` Mario Limonciello (AMD)
2026-04-01 18:52 ` Borislav Petkov
2026-04-01 19:34 ` [tip: x86/platform] " tip-bot2 for Yazen Ghannam
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=20260401111701.536cfda1@endymion \
--to=jdelvare@suse.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=superm1@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