From: Philipp Miedl <philipp.miedl@tik.ee.ethz.ch>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: alex@digriz.org.uk, jun.nakajima@intel.com,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Delayed acpi frequency governor call
Date: Wed, 25 Jan 2017 10:48:40 +0100 [thread overview]
Message-ID: <47c8a3d0-c871-c211-f951-2b6607310cff@tik.ee.ethz.ch> (raw)
In-Reply-To: <20170125032341.GC20040@vireshk-i7>
On 25.01.2017 04:23, Viresh Kumar wrote:
> On 24-01-17, 15:49, Philipp Miedl wrote:
>> Can you please describe how things changed from version 4.4 to 4.9 - I'm not
>> sure if I understand correctly.
>> Before 4.7 the governor was just running as a kernel process and triggered
>> by the (free running) timers and
>> now its hooked with the scheduler. So the scheduler ensures that the
>> governor work is not delayed?!
> Now the cpufreq callbacks gets called from within the scheduler every few
> milliseconds. And once we have crossed the sampling-rate time, we reevaluate the
> frequency. Though ondemand/conservative governors still used workqueue until
> very recently for most of the platforms. Recently it is replaced by a RT thread.
>
Ok got it now. Thanks a lot for your help!
--
--------------------------------------------------------------------
| Philipp Miedl |
| PhD Student @ Computer Engineering and Networks Laboratory |
| ETH Zurich, ETZG76, Gloriastrasse 35, 8092 Zurich, Switzerland |
| mail: philipp.miedl@ee.tik.ethz.ch phone: +41 44 632 70 61 |
--------------------------------------------------------------------
prev parent reply other threads:[~2017-01-25 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8ee7078-ad5a-0a23-66ae-620c507300e5@tik.ee.ethz.ch>
2017-01-20 10:07 ` Delayed acpi frequency governor call Viresh Kumar
2017-01-20 15:27 ` Philipp Miedl
2017-01-23 10:11 ` Viresh Kumar
2017-01-23 14:24 ` Philipp Miedl
2017-01-24 4:22 ` Viresh Kumar
2017-01-24 14:49 ` Philipp Miedl
2017-01-25 3:23 ` Viresh Kumar
2017-01-25 9:48 ` Philipp Miedl [this message]
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=47c8a3d0-c871-c211-f951-2b6607310cff@tik.ee.ethz.ch \
--to=philipp.miedl@tik.ee.ethz.ch \
--cc=alex@digriz.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-pm@vger.kernel.org \
--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