[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1502725671.2042.137.camel@hpe.com>
Date: Mon, 14 Aug 2017 15:57:35 +0000
From: "Kani, Toshimitsu" <toshi.kani@....com>
To: "bp@...en8.de" <bp@...en8.de>
CC: "rjw@...ysocki.net" <rjw@...ysocki.net>,
"lenb@...nel.org" <lenb@...nel.org>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>
Subject: Re: [PATCH v2 4/7] ghes_edac: avoid multiple calls to dmi_walk()
On Fri, 2017-08-11 at 11:04 +0200, Borislav Petkov wrote:
> On Mon, Aug 07, 2017 at 05:59:15PM +0000, Kani, Toshimitsu wrote:
> > I think we should keep the current scheme, which registers an mci
> > for
>
> No we shouldn't.
>
> > each GHES entry. ghes_edac_report_mem_error() expects that error-
> > reporting is serialized per a GHES entry. Sharing a single mci
> > among all GHES entries / error interfaces might lead to a race
> > condition.
>
> See how I solved it in my patchset and feel free to reuse it.
Hmm... Sorry, I failed to see how your patchset solved it. Would you
mind to explain how it is done?
Thanks!
-Toshi
Powered by blists - more mailing lists