Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 25, 2014 at 10:18:03PM +0000, rosslagerwall@xxxxxxxxx wrote:
> On Tue, Mar 25, 2014 at 03:04:16PM -0700, Vinson Lee wrote:
> > Hi.
> > 
> > Please backport upstream commit 8673b83bf2f013379453b4779047bf3c6ae387e4 
> > "acpi-cpufreq: set current frequency based on target P-State" to stable 
> > kernels 3.7 and earlier. This patch enables the kernel to control 
> > P-states on several platforms. Without this patch, the kernel was unable 
> > to control P-states on the same platforms.
> > 
> > The upstream patch cleanly applies to 3.7.
> > 
> > A backported patch is needed with the removal of SYSTEM_AMD_MSR_CAPABLE 
> > for kernels 3.6 and earlier.
> > 
> 
> I seem to recall that the problem was a regression introduced by commit
> 5a1c0228 (cpufreq: Avoid calling cpufreq driver's target() routine if
> target_freq == policy->cur) which was introduced in the 3.8 cycle.  Are
> you sure it is necessary for kernels < 3.8?

Given the lack of response here, I'm dropping these from my queue.  If
someone wants them back in, please resend after responding to this...

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]