[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c92bc059-0e9e-42b1-a6fc-9f9acd254a77@intel.com>
Date: Tue, 8 Apr 2025 08:45:23 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Borislav Petkov <bp@...en8.de>, Mario Limonciello <superm1@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>, 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 2/2] x86/CPU/AMD: Print the reason for the last reset
On 4/7/25 14:46, Borislav Petkov wrote:
> On Mon, Apr 07, 2025 at 01:56:57PM -0500, Mario Limonciello wrote:
>> Boris, your thoughts please?
> Right, how hard would it be to decode those as much as possible without
> having users go look somewhere first?
>
> I mean, we can always go look somewhere for more info but for starters we
> should display as much useful information as possible.
Yeah, it's pretty cruel to have all the data to programmatically decode
the bits in the kernel tree and then only use it for documentation.
Big ack from me to decode this for users as much as possible.
Powered by blists - more mailing lists