linux-kernel - Re: [PATCH v2 2/2] x86/CPU/AMD: Print the reason for the last reset

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: <9be828dc-94d0-4760-a78f-e8f92d92bcbd@intel.com>
Date: Tue, 8 Apr 2025 11:28:17 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Mario Limonciello <superm1@...nel.org>, 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/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";

?