[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170816140350.o573iksqgkj4m5xu@pd.tnic>
Date: Wed, 16 Aug 2017 16:03:50 +0200
From: Borislav Petkov <bp@...en8.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Luck, Tony" <tony.luck@...el.com>,
"Kani, Toshimitsu" <toshi.kani@....com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"lenb@...nel.org" <lenb@...nel.org>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"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 Wed, Aug 16, 2017 at 09:59:01AM -0400, Steven Rostedt wrote:
> Should the above be:
>
> if (WARN_ON_ONCE(in_nmi()))
> return;
>
> To prevent a deadlock? Or do we not care?
Yeah, better this way.
> What's the likelihood of two calls to ghes_edac_register being done
> simultaneously? Because two calls at the same time will get past this.
Well, that thing gets called per GHES platform device and last time I
checked they do get probed back-to-back but I'll check that again.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists