From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/MCE/AMD: Always give PANIC severity for UC errors in kernel context
Date: Wed, 27 Sep 2017 17:26:35 +0200 [thread overview]
Message-ID: <20170927152635.eihhaeumf43gprkq@pd.tnic> (raw)
In-Reply-To: <BN6PR1201MB0131AC2EE7B4D0D674EEF8BFF8780@BN6PR1201MB0131.namprd12.prod.outlook.com>
On Wed, Sep 27, 2017 at 03:17:51PM +0000, Ghannam, Yazen wrote:
> Generally, we can use the IN_KERNEL_RECOV context to show that the error
> is recoverable versus IN_KERNEL which we can consider unrecoverable.
>
> Specifically, the Intel SER and AMD SUCCOR features represent the same
> thing (MCA Recovery). I'll send another patch for enabling recovery on
> AMD SUCCOR systems. I want to keep this patch as just a bug fix.
Ok, but then do not mention IN_KERNEL_RECOV here as it only confuses: is
it a recoverable error or is it not? /me scratches head...
> Sure, I'll do this in another patch. I want to keep this as a bug fix
> to apply to the stable branches.
Sure.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-09-27 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 14:07 Yazen Ghannam
2017-09-26 12:01 ` Borislav Petkov
2017-09-26 15:21 ` Ghannam, Yazen
2017-09-26 22:20 ` Borislav Petkov
2017-09-27 15:17 ` Ghannam, Yazen
2017-09-27 15:26 ` Borislav Petkov [this message]
2017-11-21 15:05 [PATCH] x86/MCE/AMD: Always give panic " 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=20170927152635.eihhaeumf43gprkq@pd.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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®