From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>, Mario Limonciello <superm1@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH 2/2] x86/CPU/AMD: Print the reason for the last reset
Date: Tue, 8 Apr 2025 08:45:23 -0700 [thread overview]
Message-ID: <c92bc059-0e9e-42b1-a6fc-9f9acd254a77@intel.com> (raw)
In-Reply-To: <20250407214624.GEZ_RHsCPSfyM4r56w@fat_crate.local>
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.
prev parent reply other threads:[~2025-04-08 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 16:25 [PATCH 1/2] Documentation: Add AMD Zen debugging document Mario Limonciello
2025-04-07 16:25 ` [PATCH 2/2] x86/CPU/AMD: Print the reason for the last reset Mario Limonciello
2025-04-07 18:46 ` Ingo Molnar
2025-04-07 18:56 ` Mario Limonciello
2025-04-07 19:04 ` Ingo Molnar
2025-04-07 21:46 ` Borislav Petkov
2025-04-08 7:09 ` Ingo Molnar
2025-04-08 7:17 ` Ingo Molnar
2025-04-08 15:45 ` Dave Hansen [this message]
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=c92bc059-0e9e-42b1-a6fc-9f9acd254a77@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=superm1@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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