From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nick Piggin <npiggin@suse.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
linuxppc-dev@lists.ozlabs.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/3] cpufreq: pmac64: speed up frequency switch
Date: Mon, 12 Aug 2013 11:07:48 +1000 [thread overview]
Message-ID: <1376269668.32100.148.camel@pasglop> (raw)
In-Reply-To: <1374614043.3916.84.camel@pasglop>
On Wed, 2013-07-24 at 07:14 +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2013-07-23 at 23:20 +0200, Rafael J. Wysocki wrote:
> > All looks good in the patchset from 10000 feet (or more), but I need
> > Ben to speak here.
>
> I want to give it a quick spin on the HW here, I'll ack then. But yes,
> it looks good.
Seems to work here on the quad G5.
However, If I use on-demand, there's a huge latency of switch as far as
I can tell (about 10s) after I start/stop a bunch of CPU eaters... I
quite like how the userspace "powernowd" which I used to use switches
more aggressively.
Is that expected ?
Cheers,
Ben.
next prev parent reply other threads:[~2013-08-12 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 20:24 [PATCH 1/3] cpufreq: pmac64: speed up frequency switch Aaro Koskinen
2013-07-23 20:24 ` [PATCH 2/3] cpufreq: pmac64: re-estimate G5 cpufreq transition latency Aaro Koskinen
2013-07-24 5:34 ` Viresh Kumar
2013-07-24 10:18 ` Aaro Koskinen
2013-07-24 10:45 ` Viresh Kumar
2013-07-23 20:24 ` [PATCH 3/3] cpufreq: pmac64: enable cpufreq on iMac G5 (iSight) model Aaro Koskinen
2013-07-24 5:34 ` Viresh Kumar
2013-07-23 21:20 ` [PATCH 1/3] cpufreq: pmac64: speed up frequency switch Rafael J. Wysocki
2013-07-23 21:14 ` Benjamin Herrenschmidt
2013-08-12 1:07 ` Benjamin Herrenschmidt [this message]
2013-08-15 20:10 ` Aaro Koskinen
2013-08-15 22:14 ` Benjamin Herrenschmidt
2013-07-24 5:32 ` Viresh Kumar
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=1376269668.32100.148.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aaro.koskinen@iki.fi \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@suse.de \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).