On Tuesday, July 21, 2015 10:41:13 AM Lukasz Anaczkowski wrote: > Scaling for Knights Landing is same as the default scaling (100000). > When Knigts Landing support was added to the pstate driver, this > parameter was omitted resulting in a kernel panic during boot. > > Reported-by: Yasuaki Ishimatsu <yishi...@redhat.com> > Signed-off-by: Dasaratharaman Chandramouli > <dasaratharaman.chandramo...@intel.com> > Signed-off-by: Lukasz Anaczkowski <lukasz.anaczkow...@intel.com>
Queued up for 4.3, thanks! > --- > drivers/cpufreq/intel_pstate.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c > index 15ada47..fcb929e 100644 > --- a/drivers/cpufreq/intel_pstate.c > +++ b/drivers/cpufreq/intel_pstate.c > @@ -681,6 +681,7 @@ static struct cpu_defaults knl_params = { > .get_max = core_get_max_pstate, > .get_min = core_get_min_pstate, > .get_turbo = knl_get_turbo_pstate, > + .get_scaling = core_get_scaling, > .set = core_set_pstate, > }, > }; > -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/