[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251217212134.GD1263950@yaz-khff2.amd.com>
Date: Wed, 17 Dec 2025 16:21:34 -0500
From: Yazen Ghannam <yazen.ghannam@....com>
To: Mario Limonciello <superm1@...nel.org>
Cc: "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
Jean Delvare <jdelvare@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H . Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/7] firmware: dmi: Read additional information when
decoding DMI table
On Wed, Dec 17, 2025 at 03:09:33PM -0600, Mario Limonciello wrote:
> On 12/17/25 3:03 PM, Yazen Ghannam wrote:
> > On Tue, Dec 16, 2025 at 06:33:50AM -0600, Mario Limonciello (AMD) wrote:
> > > Type 40 entries (Additional information) are summarized in section
> > > 7.41 as part of the SMBIOS specification. Save these entries when
> > > decoding the DMI tables.
> > >
> >
> > Why can't an interested user just use dmidecode?
> >
> > Thanks,
> > Yazen
>
> They could. The reason for doing it in this series is the same reason for
> the one that we did the S5 bit.
>
> It shows up in the logs, you can tie regressions to the AGESA version at
> specifically at the time of the failure if they've done BIOS updates since
> then.
Yes, right. Sorry, I mixed this up with the debugfs patch.
We need to save it here so the init code can find it.
But why do we need a debugfs entry for it?
Thanks,
Yazen
Powered by blists - more mailing lists