From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Steve Muckle <steve.muckle@linaro.org>,
Juri Lelli <juri.lelli@arm.com>, Ingo Molnar <mingo@kernel.org>
Subject: [PATCH 0/2] cpufreq / sched: Rework of cpufreq_update_util() arguments
Date: Wed, 10 Aug 2016 02:43 +0200 [thread overview]
Message-ID: <4498725.ix9jPCHteg@vostro.rjw.lan> (raw)
Hi,
There were some comments on the "cpufreq / sched: cpufreq_update_util() flags
and iowait boosting" series I sent some time ago and I wanted to address them,
but for this purpose I had to combine patches [1-2,4/7] from that series
into one and make some changes on top of that.
Then I thought it would be better to send that separately from the iowait
boost part of that series, so here it goes.
[1/2] Removes the util and max args from cpufreq_update_util() and governor
callbacks and adds a flags argument instead of them. That argument
is then used to handle RT and DL in schedutil and the utilization data
are accessed by it directly (so it is non-modular now to avoid exporting
the scheduler internals to modules).
[2/2] Replaces the time argument of cpufreq_update_util() with an rq pointer
which allows some simplifications to be made.
There should be no changes in behavior as a result of this.
Thanks,
Rafael
next reply other threads:[~2016-08-10 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 0:43 Rafael J. Wysocki [this message]
2016-08-10 1:09 ` [PATCH 1/2] cpufreq / sched: Pass flags to cpufreq_update_util() Rafael J. Wysocki
2016-08-10 1:49 ` [Update][PATCH " Rafael J. Wysocki
2016-08-11 18:03 ` Steve Muckle
2016-08-11 18:05 ` Steve Muckle
2016-08-10 1:11 ` [PATCH 2/2] cpufreq / sched: Check cpu_of(rq) in cpufreq_update_util() Rafael J. Wysocki
2016-08-11 22:34 ` Steve Muckle
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=4498725.ix9jPCHteg@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=steve.muckle@linaro.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