From: Mario Limonciello <superm1@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mario Limonciello <mario.limonciello@amd.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
"H . Peter Anvin" <hpa@zytor.com>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v6 0/2] AMD Zen debugging documentation
Date: Thu, 1 May 2025 16:41:45 -0500 [thread overview]
Message-ID: <20250501214147.2488164-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
Introduce documentation for debugging some issues on AMD zen hardware.
As one of the debugging techniques read and add information for
S5_RESET_STATUS register.
v6:
* Drop pre-req patches already merged to tip.git
* Use Boris' suggestion for reading S5_RESET_STATUS
Mario Limonciello (1):
Documentation: Add AMD Zen debugging document
Yazen Ghannam (1):
x86/CPU/AMD: Print the reason for the last reset
Documentation/arch/x86/amd-debugging.rst | 362 +++++++++++++++++++++++
Documentation/arch/x86/index.rst | 1 +
Documentation/arch/x86/resume.svg | 4 +
Documentation/arch/x86/suspend.svg | 4 +
arch/x86/include/asm/amd/fch.h | 1 +
arch/x86/kernel/cpu/amd.c | 53 ++++
6 files changed, 425 insertions(+)
create mode 100644 Documentation/arch/x86/amd-debugging.rst
create mode 100644 Documentation/arch/x86/resume.svg
create mode 100644 Documentation/arch/x86/suspend.svg
--
2.43.0
next reply other threads:[~2025-05-01 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 21:41 Mario Limonciello [this message]
2025-05-01 21:41 ` [PATCH v6 1/2] Documentation: Add AMD Zen debugging document Mario Limonciello
2025-05-01 21:41 ` [PATCH v6 2/2] x86/CPU/AMD: Print the reason for the last reset Mario Limonciello
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=20250501214147.2488164-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=Shyam-sundar.S-k@amd.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@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).