From: Greg KH <greg@kroah.com>
To: rosslagerwall@gmail.com
Cc: Vinson Lee <vlee@twopensource.com>,
stable@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [stable request <=3.7] acpi-cpufreq: set current frequency based on target P-State
Date: Fri, 11 Apr 2014 09:05:43 -0700 [thread overview]
Message-ID: <20140411160543.GC31676@kroah.com> (raw)
In-Reply-To: <20140325221803.GA32518@hobo.lan>
On Tue, Mar 25, 2014 at 10:18:03PM +0000, rosslagerwall@gmail.com 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
next prev parent reply other threads:[~2014-04-11 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 2:14 [stable request <=3.5] acpi-cpufreq: set current frequency based on target P-State Vinson Lee
2013-12-20 8:19 ` Ross Lagerwall
2014-03-25 22:04 ` [stable request <=3.7] " Vinson Lee
2014-03-25 22:04 ` [PATCH] " Vinson Lee
2014-03-25 22:18 ` [stable request <=3.7] " rosslagerwall
2014-03-25 22:53 ` Vinson Lee
2014-03-26 7:22 ` rosslagerwall
2014-04-11 16:05 ` Greg KH [this message]
2014-03-31 8:50 ` Luís Henriques
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140411160543.GC31676@kroah.com \
--to=greg@kroah.com \
--cc=cpufreq@vger.kernel.org \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rosslagerwall@gmail.com \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vlee@twopensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.