From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>, Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
Carlos Bilbao <carlos.bilbao@amd.com>,
x86@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Dump stack after certain machine checks
Date: Mon, 31 Oct 2022 11:30:03 +0100 [thread overview]
Message-ID: <Y1+jqyh8dAz6tsTr@zn.tnic> (raw)
In-Reply-To: <20220922195136.54575-1-tony.luck@intel.com>
On Thu, Sep 22, 2022 at 12:51:34PM -0700, Tony Luck wrote:
> I've only updated the Intel severity calculation to use this new
> severity level. I'm not sure if AMD also has situations where this would
> be useful. If so, then mce_severity_amd() would need to be updated too
> to return different severity for IN_KERNEL and IN_KERNEL_RECOV cases.
I'd look into Yazen's direction for that...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-10-31 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:51 [PATCH 0/2] Dump stack after certain machine checks Tony Luck
2022-09-22 19:51 ` [PATCH 1/2] x86/mce: Use severity table to handle uncorrected errors in kernel Tony Luck
2022-10-31 16:15 ` [tip: ras/core] " tip-bot2 for Tony Luck
2022-09-22 19:51 ` [PATCH 2/2] x86/mce: Dump the stack for recoverable machine checks in kernel context Tony Luck
2022-10-31 16:44 ` Borislav Petkov
2022-10-31 17:13 ` Luck, Tony
2022-10-31 18:36 ` Borislav Petkov
2022-10-31 19:20 ` Luck, Tony
2022-10-31 10:30 ` Borislav Petkov [this message]
2022-11-01 17:36 ` [PATCH 0/2] Dump stack after certain machine checks Yazen Ghannam
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=Y1+jqyh8dAz6tsTr@zn.tnic \
--to=bp@alien8.de \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=carlos.bilbao@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.