From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Youquan Song <youquan.song@intel.com>
Subject: Re: [PATCH] x86/mce: Add Skylake quirk for patrol scrub reported errors
Date: Wed, 24 Mar 2021 16:00:04 +0100 [thread overview]
Message-ID: <20210324150004.GG5010@zn.tnic> (raw)
In-Reply-To: <20210322223710.307123-1-tony.luck@intel.com>
On Mon, Mar 22, 2021 at 03:37:10PM -0700, Tony Luck wrote:
> From: Youquan Song <youquan.song@intel.com>
>
> Skylake has a mode where the system administrator can use a BIOS setup
> option to request that the memory controller report uncorrected errors
> found by the patrol scrubber as corrected. This results in them being
> signalled using CMCI, which is less disruptive than a machine check.
>
> Add a quirk to detect that a "corrected" error is actually a downgraded
> uncorrected error with model specific checks for the "MSCOD" signature in
> MCi_STATUS and that the error was reported from a memory controller bank.
>
> Adjust the severity to MCE_AO_SEVERITY so that Linux will try to take
> the affected page offline.
>
> [Tony: Wordsmith commit comment]
>
> Signed-off-by: Youquan Song <youquan.song@intel.com>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
>
> ---
> Repost ... looks like this got lost somewhere.
Yeah, into
fd258dc4442c ("x86/mce: Add Skylake quirk for patrol scrub reported errors")
:-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-03-24 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 22:37 [PATCH] x86/mce: Add Skylake quirk for patrol scrub reported errors Tony Luck
2021-03-24 15:00 ` Borislav Petkov [this message]
2021-03-24 15:35 ` Luck, Tony
-- strict thread matches above, loose matches on Subject: below --
2020-06-15 18:40 Tony Luck
2020-06-16 19:29 ` Borislav Petkov
2020-06-16 22:33 ` Luck, Tony
2020-06-17 7:41 ` Borislav Petkov
2020-06-17 18:49 ` Luck, Tony
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=20210324150004.GG5010@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=youquan.song@intel.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.