From: Mario Limonciello <superm1@kernel.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>, Borislav Petkov <bp@alien8.de>
Cc: Jean Delvare <jdelvare@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry
Date: Wed, 28 Jan 2026 09:27:37 -0600 [thread overview]
Message-ID: <2bc5797b-156d-4f70-85b9-092200fefde4@kernel.org> (raw)
In-Reply-To: <20260128143920.GA551269@yaz-khff2.amd.com>
On 1/28/26 8:39 AM, Yazen Ghannam wrote:
> 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
Like all things - it's a case by case basis based upon the ticket and
what's wrong.
I don't see any problem with just "grep AGESA" though.
next prev parent reply other threads:[~2026-01-28 15:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 21:30 [PATCH v5 0/5] Print AGESA version at bootup Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 1/5] firmware: dmi: Correct an indexing error in dmi.h Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 2/5] firmware: dmi: Adjust dmi_decode() to use enums Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 3/5] firmware: dmi: Add missing DMI entry types Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 4/5] firmware: dmi: Add pr_fmt() for dmi_scan.c Mario Limonciello (AMD)
2026-01-23 21:30 ` [PATCH v5 5/5] x86/CPU/AMD: Print AGESA string from DMI additional information entry Mario Limonciello (AMD)
2026-01-26 13:07 ` Borislav Petkov
2026-01-26 15:15 ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 15:40 ` Borislav Petkov
2026-01-26 16:41 ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 16:54 ` Borislav Petkov
2026-01-28 14:39 ` Yazen Ghannam
2026-01-28 15:27 ` Mario Limonciello [this message]
2026-03-15 13:14 ` Borislav Petkov
2026-03-15 15:14 ` Mario Limonciello
2026-03-15 20:56 ` Borislav Petkov
2026-03-17 2:33 ` Mario Limonciello
2026-03-17 18:24 ` Borislav Petkov
2026-03-17 18:28 ` Mario Limonciello
2026-03-17 19:18 ` Borislav Petkov
2026-03-31 17:59 ` Jean Delvare
2026-03-31 18:09 ` Borislav Petkov
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=2bc5797b-156d-4f70-85b9-092200fefde4@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.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