lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260128143920.GA551269@yaz-khff2.amd.com>
Date: Wed, 28 Jan 2026 09:39:20 -0500
From: Yazen Ghannam <yazen.ghannam@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: "Mario Limonciello (AMD) (kernel.org)" <superm1@...nel.org>,
	Jean Delvare <jdelvare@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI
 additional information entry

On Mon, Jan 26, 2026 at 05:54:12PM +0100, Borislav Petkov wrote:
> On Mon, Jan 26, 2026 at 10:41:21AM -0600, Mario Limonciello (AMD) (kernel.org) wrote:
> > Well now you see why I was proposing the x86/amd: prefix in the first place.
> > It could be no slicing and dicing and with that prefix:
> > 
> > x86/amd: AGESA!V9 StrixPI-FP8 1.0.0.1d
> 
> So the prefix tells so that it is somewhere from x86/.../amd.
> 
> The "AGESA:" prefix tells you it is AGESA.
> 
> I don't see how the "x86/amd" prefix works here...
> 

Mario, what's your intended debug flow?

Do you want to grab any and all messages related to AMD and then go
through them? So here you'd like "x86/amd" or something similar as a
first pass filter.

Or do you look for specific pieces of data, as needed? So here you'd
just look for "AGESA" if you want that or "reset reason", etc.

Thanks,
Yazen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ