From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Guilherme Salazar <gmesalazar@gmail.com>
Cc: linux-pm@vger.kernel.org, dirk.brandewie@gmail.com
Subject: Re: [PATCH] cpufreq/intel_pstate: Change to scale off of max P-state
Date: Tue, 20 Aug 2013 11:37:41 -0700 [thread overview]
Message-ID: <5213B775.6090008@gmail.com> (raw)
In-Reply-To: <loom.20130801T194134-745@post.gmane.org>
On 08/01/2013 10:56 AM, Guilherme Salazar wrote:
> <dirk.brandewie <at> gmail.com> writes:
>
>>
>> From: Dirk Brandewie <dirk.j.brandewie <at> intel.com>
>>
>> Change to using max P-state instead of max turbo P-state. This change
>> resolves two issues.
>>
>> On a quiet system intel_pstate can fail to respond to a load change.
>> https://bugzilla.kernel.org/show_bug.cgi?id=59481
>>
>> On CPU SKUs that have a limited number of P-states and no turbo range
>> intel_pstate fails to select the highest available P-state.
>>
>> This change is suitable for stable v3.9+
>>
>> Reported-by: arjan <at> linux.intel.com
>> Reported-by: dsmythies <at> telus.net
>> Tested-by: arjan <at> linux.intel.com
>> Tested-by: dsmythies <at> telus.net
>>
>> CC: stable <at> vger.kernel.org
>> CC: dsmythies <at> telus.net
>> Signed-off-by: Dirk Brandewie <dirk.j.brandewie <at> intel.com>
>
> Hi,
>
> I've just tested the patch and, even though it works (the frequency now sits
> around 1.3-1.5 GHz), I noticed that if I suspend the laptop and then resume
> it, the abnormal behavior (frequency sitting above 2 GHz) returns.
>
There is a separate bug against the suspend resume behaviour. It is coming
from a bug in the cpufreq core.
https://bugzilla.kernel.org/show_bug.cgi?id=59781
The fix is disscussed in https://lkml.org/lkml/2013/7/29/692 and is queue for 3.12
> Before suspending, the value in
> /sys/devices/system/cpu/intel_pstate/min_perf_pct was 37; afterwards, 100.
>
> cpuinfo: http://pastebin.com/C6zR90HC
>
> I'd be glad to give any further details.
>
> Best,
> Guilherme
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-08-20 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 15:48 [PATCH] cpufreq/intel_pstate: Change to scale off of max P-state dirk.brandewie
2013-07-19 3:53 ` Viresh Kumar
2013-08-01 17:56 ` Guilherme Salazar
2013-08-20 18:37 ` Dirk Brandewie [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-18 15:58 dirk.brandewie
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=5213B775.6090008@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=gmesalazar@gmail.com \
--cc=linux-pm@vger.kernel.org \
/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.