public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>, Jean Delvare <jdelvare@suse.com>,
	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
Subject: Re: [PATCH 5/5] x86/amd_node: Output the AGESA version to the logs
Date: Mon, 15 Dec 2025 15:25:31 -0600	[thread overview]
Message-ID: <65cfc33d-cd8e-41d1-82b7-58a4fcb01207@kernel.org> (raw)
In-Reply-To: <20251215212338.GC355290@yaz-khff2.amd.com>

On 12/15/25 3:23 PM, Yazen Ghannam wrote:
> On Sun, Dec 14, 2025 at 12:53:09PM -0600, Mario Limonciello (AMD) wrote:
>> On AMD Zen platforms that are running AGESA, there is sometimes
>> DMI additional string for the AGESA version that can be helpful when
>> debugging an issue.  If this string is found output to kernel logs.
>>
>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>> ---
>> This is not strictly AMD node related; it was a proxy for a good location
>> for the message late enough on boot and only run on AMD Zen machines.
>> I'm open to other suggestions.
> 
> Maybe do like print_s5_reset_status_mmio() with a late_initcall()?
> 
> We could have an amd_zen_late_initcall() function in
> arch/x86/kernel/cpu/amd.c that collects appropriate functions.
> 
> We have two now:
>   - print_s5_reset_status_mmio()
>   - print_agesa_dmi_info()

Good idea, that is a more logical location.  Lemme try it out.

> 
> Thanks,
> Yazen
> 
>>   arch/x86/Kconfig           | 1 +
>>   arch/x86/kernel/amd_node.c | 8 ++++++++
>>   2 files changed, 9 insertions(+)
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 80527299f859a..eae139a91fb84 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -3116,6 +3116,7 @@ config AMD_NB
>>   config AMD_NODE
>>   	def_bool y
>>   	depends on CPU_SUP_AMD && PCI
>> +	select DMI
>>   
>>   endmenu
>>   
>> diff --git a/arch/x86/kernel/amd_node.c b/arch/x86/kernel/amd_node.c
>> index 3d0a4768d603c..575d727c5827e 100644
>> --- a/arch/x86/kernel/amd_node.c
>> +++ b/arch/x86/kernel/amd_node.c
>> @@ -9,6 +9,7 @@
>>    */
>>   
>>   #include <linux/debugfs.h>
>> +#include <linux/dmi.h>
>>   #include <asm/amd/node.h>
>>   
>>   /*
>> @@ -247,6 +248,7 @@ __setup("amd_smn_debugfs_enable", amd_smn_enable_dfs);
>>   static int __init amd_smn_init(void)
>>   {
>>   	u16 count, num_roots, roots_per_node, node, num_nodes;
>> +	const struct dmi_device *dev = NULL;
>>   	struct pci_dev *root;
>>   
>>   	if (!cpu_feature_enabled(X86_FEATURE_ZEN))
>> @@ -310,6 +312,12 @@ static int __init amd_smn_init(void)
>>   
>>   	smn_exclusive = true;
>>   
>> +	while ((dev = dmi_find_device(DMI_DEV_TYPE_ADDITIONAL, NULL, dev)))
>> +		if (!strncmp(dev->name, "AGESA", 5)) {
>> +			pr_info("%s\n", dev->name);
>> +			break;
>> +		}
>> +
>>   	return 0;
>>   }
>>   
>> -- 
>> 2.43.0
>>


      reply	other threads:[~2025-12-15 21:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-14 18:53 [PATCH 0/5] Parse SMBIOS additional entries Mario Limonciello (AMD)
2025-12-14 18:53 ` [PATCH 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2025-12-15 21:11   ` Yazen Ghannam
2025-12-15 21:24     ` Mario Limonciello
2025-12-14 18:53 ` [PATCH 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2025-12-15 21:12   ` Yazen Ghannam
2025-12-14 18:53 ` [PATCH 3/5] firmware: dmi: Read additional information when decoding DMI table Mario Limonciello (AMD)
2025-12-15  4:31   ` kernel test robot
2025-12-15  5:06   ` kernel test robot
2025-12-15 12:47   ` kernel test robot
2025-12-14 18:53 ` [PATCH 4/5] firmware: dmi: Add debugfs for additional information entries Mario Limonciello (AMD)
2025-12-14 18:53 ` [PATCH 5/5] x86/amd_node: Output the AGESA version to the logs Mario Limonciello (AMD)
2025-12-15 21:23   ` Yazen Ghannam
2025-12-15 21:25     ` Mario Limonciello [this message]

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=65cfc33d-cd8e-41d1-82b7-58a4fcb01207@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