From: Borislav Petkov <bp@alien8.de>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>,
linux-nvdimm@lists.01.org, Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: [v3,1/2] nfit, mce: only handle uncorrectable machine checks
Date: Wed, 20 Feb 2019 20:18:52 +0100 [thread overview]
Message-ID: <20190220191852.GF3447@zn.tnic> (raw)
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?
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.
> How do we end up getting called with a correctable error?
Good question. We shouldn't.
So we need to figure out here how exactly should those things interact
and whether NFIT should get all errors reported or it should put all the
correctable errors through the decay thing, see the comment at the top
of drivers/ras/cec.c
Thx for pointing that out Jeff.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [PATCH v3 1/2] nfit, mce: only handle uncorrectable machine checks
Date: Wed, 20 Feb 2019 20:18:52 +0100 [thread overview]
Message-ID: <20190220191852.GF3447@zn.tnic> (raw)
In-Reply-To: <x49lg2a2sn0.fsf@segfault.boston.devel.redhat.com>
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?
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.
> How do we end up getting called with a correctable error?
Good question. We shouldn't.
So we need to figure out here how exactly should those things interact
and whether NFIT should get all errors reported or it should put all the
correctable errors through the decay thing, see the comment at the top
of drivers/ras/cec.c
Thx for pointing that out Jeff.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2019-02-20 19:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 19:18 Borislav Petkov [this message]
2019-02-20 19:18 ` [PATCH v3 1/2] nfit, mce: only handle uncorrectable machine checks Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2019-02-21 17:09 [v3,1/2] " Borislav Petkov
2019-02-21 17:09 ` [PATCH v3 1/2] " Borislav Petkov
2019-02-21 16:11 [v3,1/2] " Jeff Moyer
2019-02-21 16:11 ` [PATCH v3 1/2] " Jeff Moyer
2019-02-20 19:47 [v3,1/2] " Borislav Petkov
2019-02-20 19:47 ` [PATCH v3 1/2] " Borislav Petkov
2019-02-20 19:40 [v3,1/2] " Dan Williams
2019-02-20 19:40 ` [PATCH v3 1/2] " Dan Williams
2019-02-20 19:39 [v3,1/2] " Borislav Petkov
2019-02-20 19:39 ` [PATCH v3 1/2] " Borislav Petkov
2019-02-20 19:26 [v3,1/2] " Jeff Moyer
2019-02-20 19:26 ` [PATCH v3 1/2] " Jeff Moyer
2019-02-20 18:59 [v3,1/2] " Jeff Moyer
2019-02-20 18:59 ` [PATCH v3 1/2] " Jeff Moyer
2019-02-20 18:59 ` Jeff Moyer
2018-11-06 18:19 [tip:x86/urgent] acpi/nfit, x86/mce: Validate a MCE's address before using it tip-bot for Borislav Petkov
2018-11-06 18:19 ` tip-bot for Vishal Verma
2018-11-06 18:18 [tip:x86/urgent] acpi/nfit, x86/mce: Handle only uncorrectable machine checks tip-bot for Borislav Petkov
2018-11-06 18:18 ` tip-bot for Vishal Verma
2018-11-06 18:07 [v3,2/2] nfit, mce: validate the mce->addr before using it Borislav Petkov
2018-11-06 18:07 ` [PATCH v3 2/2] " Borislav Petkov
2018-11-06 18:07 ` Borislav Petkov
2018-11-06 18:02 [v3,2/2] " Dan Williams
2018-11-06 18:02 ` [PATCH v3 2/2] " Dan Williams
2018-11-06 18:02 ` Dan Williams
2018-11-06 17:53 [v3,2/2] " Borislav Petkov
2018-11-06 17:53 ` [PATCH v3 2/2] " Borislav Petkov
2018-11-06 17:53 ` Borislav Petkov
2018-11-06 16:20 [v3,2/2] " Dan Williams
2018-11-06 16:20 ` [PATCH v3 2/2] " Dan Williams
2018-11-06 16:20 ` Dan Williams
2018-11-06 14:51 [v3,2/2] " Borislav Petkov
2018-11-06 14:51 ` [PATCH v3 2/2] " Borislav Petkov
2018-11-06 14:51 ` Borislav Petkov
2018-10-26 0:37 [v3,2/2] " Vishal Verma
2018-10-26 0:37 ` [PATCH v3 2/2] " Vishal Verma
2018-10-26 0:37 ` Vishal Verma
2018-10-26 0:37 [v3,1/2] nfit, mce: only handle uncorrectable machine checks Vishal Verma
2018-10-26 0:37 ` [PATCH v3 1/2] " Vishal Verma
2018-10-26 0:37 ` Vishal Verma
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=20190220191852.GF3447@zn.tnic \
--to=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@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.