Re: [PATCH v3 1/2] nfit, mce: only handle uncorrectable machine checks
On Wed, Feb 20, 2019 at 11:26 AM Jeff Moyer <jmoyer(a)redhat.com> wrote:
Borislav Petkov <bp(a)alien8.de> writes:
> Drop stable@
>
> On Wed, Feb 20, 2019 at 01:59:15PM -0500, Jeff Moyer wrote:
>> Sorry for necroposting. I thought the point of the CEC was to make sure
>> that the other registered decoders only ever saw uncorrected errors.
>
> Ha, good point! You mean drivers/ras/cec.c, right?
Yes.
> If so, then I don't think we've ever talked about connecting CEC with
> NVDIMM and whether that would make sense. Lemme add Dan.
I don't think there's a difference between MCEs for NVDIMMs and normal
DRAM. I'll let Dan confirm or deny that.
There is a difference. NVDIMMs have local tracking of discovered
poison, methods to scan for latent poison, and methods to clear. A CEC
connection, iiuc, would seem an awkward fit. Awkward because what CEC
enables is meant to be implemented natively in the hardware, and CEC
seems to have no concept of the fact that errors can be repaired.