From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Amit Kucheria <amitk@kernel.org>, Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Javi Merino <javi.merino@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Steven Rostedt <rostedt@goodmis.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Zhang Rui <rui.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, Quentin Perret <qperret@google.com>,
Lukasz Luba <lukasz.luba@arm.com>,
linux-pm@vger.kernel.org
Subject: [PATCH V3 0/2] cpufreq_cooling: Get effective CPU utilization from scheduler
Date: Thu, 19 Nov 2020 13:08:06 +0530 [thread overview]
Message-ID: <cover.1605770951.git.viresh.kumar@linaro.org> (raw)
Hi,
This patchset makes the cpufreq_cooling driver reuse the CPU utilization
metric provided by the scheduler instead of depending on idle and busy
times of a CPU, which aren't that accurate to measure the busyness of a
CPU for the next cycle. More details can be seen in the commit log of
patch 2/2.
V2->V3:
- Put the scheduler helpers within ifdef CONFIG_SMP.
- Keep both SMP and !SMP implementations in the cpufreq_cooling driver.
- Improved commit log with testing related information.
--
Viresh
Viresh Kumar (2):
sched/core: Rename and move schedutil_cpu_util() to core.c
thermal: cpufreq_cooling: Reuse sched_cpu_util() for SMP platforms
drivers/thermal/cpufreq_cooling.c | 68 ++++++++++++++----
include/linux/sched.h | 21 ++++++
kernel/sched/core.c | 115 +++++++++++++++++++++++++++++
kernel/sched/cpufreq_schedutil.c | 116 +-----------------------------
kernel/sched/fair.c | 6 +-
kernel/sched/sched.h | 31 +-------
6 files changed, 199 insertions(+), 158 deletions(-)
base-commit: 3650b228f83adda7e5ee532e2b90429c03f7b9ec
--
2.25.0.rc1.19.g042ed3e048af
next reply other threads:[~2020-11-19 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 7:38 Viresh Kumar [this message]
2020-11-19 7:38 ` [PATCH V3 1/2] sched/core: Rename and move schedutil_cpu_util() to core.c Viresh Kumar
2020-11-19 12:30 ` Rafael J. Wysocki
2020-11-23 10:04 ` Viresh Kumar
2020-11-23 10:29 ` Rafael J. Wysocki
2020-11-19 7:38 ` [PATCH V3 2/2] thermal: cpufreq_cooling: Reuse sched_cpu_util() for SMP platforms Viresh Kumar
2020-11-20 14:51 ` Lukasz Luba
2020-11-23 10:41 ` Viresh Kumar
2020-11-23 11:34 ` Lukasz Luba
2020-11-23 15:32 ` Lukasz Luba
2020-11-24 4:56 ` Viresh Kumar
2020-12-01 17:25 ` Valentin Schneider
2020-12-07 9:13 ` 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=cover.1605770951.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=amit.kachhap@gmail.com \
--cc=amitk@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=javi.merino@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@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).