[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5788aca2-2565-4c7d-9760-6a08509eb014@kernel.org>
Date: Tue, 8 Apr 2025 13:34:30 -0500
From: Mario Limonciello <superm1@...nel.org>
To: Dave Hansen <dave.hansen@...el.com>, Borislav Petkov <bp@...en8.de>
Cc: Jonathan Corbet <corbet@....net>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Yazen Ghannam <yazen.ghannam@....com>,
Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH v2 2/2] x86/CPU/AMD: Print the reason for the last reset
On 4/8/2025 1:28 PM, Dave Hansen wrote:
> On 4/8/25 11:19, Mario Limonciello wrote:
>> I think it's still valuable to have it in documentation for anyone who
>> wants to read more about this. As we get issues that come out of the
>> woodwork I could see people punching the string into a search engine and
>> then being spit at debugging.rst and we can adjust documentation to tell
>> them what to do with it when it's not clear.
>
> How would that work when the documentation:
>
>> +31, Internal, SW sync flood event
>
> and the string don't match:
>
>> + if (value & BIT(31))
>> + return "software sync flood event";
>
> ?
Good catch.
If we're in agreement in the value of having the strings in the kernel
and then also in this table I'll make sure both sets of strings are the
same.
Powered by blists - more mailing lists