From: "Arnd Bergmann" <arnd@arndb.de>
To: "Magnus Lindholm" <linmag7@gmail.com>,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Matt Turner" <mattst88@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
macro@redhat.com, "Michael Cree" <mcree@orcon.net.nz>,
"Ivan Kokshaysky" <ink@unseen.parts>
Subject: Re: [PATCH v2] alpha: machine check handler for tsunami
Date: Wed, 23 Apr 2025 21:58:40 +0200 [thread overview]
Message-ID: <41157e81-0dd9-4950-b9b2-245c0007d2bd@app.fastmail.com> (raw)
In-Reply-To: <20250423194958.30715-1-linmag7@gmail.com>
On Wed, Apr 23, 2025, at 21:21, Magnus Lindholm wrote:
> This patch is an attempt to implement a machine check handler with detailed
> information on error conditions in the event of a machine check exception
> on the tsunami platform. This work is inspired by how machine check
> exceptions are handled on the titan family. This patch implements
> processing of the logout frames that is generated in the event of a
> machine check. The logout frame contains platform specific information
> and is helpful in pinpointing the source that triggered the exception
> or fault. Some faults are recoverable, such as a correctable ECC error,
> but others may not be possible to recover from. As Alpha hardware is aging
> we may see more errors due to failing hardware and proper machine check
> handling can assist in detecting and diagnosing such errors. I hope that
> someone finds this useful, any feedback is much appreciated.
Should this perhaps be part of drivers/edac/ ?
ARnd
next prev parent reply other threads:[~2025-04-23 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:21 Magnus Lindholm
2025-04-23 19:58 ` Arnd Bergmann [this message]
2025-04-24 20:38 ` Magnus Lindholm
2025-05-05 5:36 ` kernel test robot
2025-05-06 19:46 ` Magnus Lindholm
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=41157e81-0dd9-4950-b9b2-245c0007d2bd@app.fastmail.com \
--to=arnd@arndb.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@unseen.parts \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@redhat.com \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=paulmck@kernel.org \
--cc=richard.henderson@linaro.org \
/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
all inboxes | Powered by JetHome®