On Wednesday, December 09, 2015 08:53:55 AM Jacob Pan wrote: > On Wed, 9 Dec 2015 08:31:12 -0500 > Prarit Bhargava <[email protected]> wrote: > > > Intel RAPL initialized on several systems where the BIOS lock bit (msr > > 0x610, bit 63) was set. This occured because the return value of > > rapl_read_data_raw() was being checked, rather than the value of the > > variable passed in, locked. > > > > This patch properly implments the rapl_read_data_raw() call to check > > the variable locked, and now the Intel RAPL driver outputs the > > warning: > > > > intel_rapl: RAPL package 0 domain package locked by BIOS > > > > and does not initialize for the package. > > > > Cc: "Rafael J. Wysocki" <[email protected]> > > Cc: Jacob Pan <[email protected]> > > Cc: Radivoje Jovanovic <[email protected]> > > Cc: Seiichi Ikarashi <[email protected]> > > Cc: Mathias Krause <[email protected]> > > Cc: Ajay Thomas <[email protected]> > > Signed-off-by: Prarit Bhargava <[email protected]> > > > > [v2]: fix brackets > > Acked-by: Jacob Pan <[email protected]>
OK, I've put it into my bleeding-edge branch as 4.5 candidate, but do we want it in "stable" and therefore should it be pushed for 4.4? Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
