[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3a56071a7b2c157698ed781d09e47051e3974958.camel@linux.intel.com>
Date: Tue, 05 Nov 2019 13:21:05 -0800
From: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: tony.luck@...el.com, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, bberg@...hat.com, x86@...nel.org,
linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
hdegoede@...hat.com, ckellner@...hat.com
Subject: Re: [RFC][PATCH] x86, mce, therm_throt: Optimize notifications of
thermal throttle
On Tue, 2019-11-05 at 21:56 +0100, Borislav Petkov wrote:
> On Tue, Nov 05, 2019 at 12:36:32PM -0800, Srinivas Pandruvada wrote:
> > > That wants to be a bool judging by the context it is used in.
> >
> > I can change to bool, just didn't use it
> > https://yarchive.net/comp/linux/bool.html
>
> And are you using it in a union or where the size of bool - which is
> implementation-specific - plays any role, esp. in your particular use
> case?
No.
>
> > They are architectural MSRs and the fact that we are getting called
> > means that they are enabled by looking at CPUID bits.
>
> If the CPUID bits guarantees their presence, then the error handling
> is
> not absolutely necessary.
>
> Thx.
>
Powered by blists - more mailing lists