From: Joel Fernandes <joelaf@google.com>
To: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelaf@google.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2 0/2] Make iowait_boost optional and default to policy
Date: Thu, 18 May 2017 23:23:42 -0700 [thread overview]
Message-ID: <20170519062344.27692-1-joelaf@google.com> (raw)
iowait_boost is causing power regression on our arm64 SoC. Really going to max
frequency is bad for power on mobile devices and not wise.
These patches make it optional and default to what the policy suggests coming
from the cpufreq driver as input to the governor.
Here are some power numbers collected on an arm64 based Qualcomm SoC on a mobile
device running a YouTube video for 30 seconds:
Before: 8.042533 mWh
After: 7.948377 mWh
Energy savings is ~1.2%
Joel Fernandes (2):
cpufreq: Make iowait boost a policy option
sched: Use iowait boost policy option in schedutil
drivers/cpufreq/intel_pstate.c | 1 +
include/linux/cpufreq.h | 3 +++
kernel/sched/cpufreq_schedutil.c | 32 ++++++++++++++++++++++++++++++++
3 files changed, 36 insertions(+)
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
--
2.13.0.303.g4ebf302169-goog
next reply other threads:[~2017-05-19 6:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 6:23 Joel Fernandes [this message]
2017-05-19 6:23 ` [PATCH v2 1/2] cpufreq: Make iowait boost a policy option Joel Fernandes
2017-05-19 9:42 ` Peter Zijlstra
2017-05-19 10:21 ` Peter Zijlstra
2017-05-19 17:04 ` Joel Fernandes
2017-05-22 8:21 ` Peter Zijlstra
2017-05-24 20:17 ` Joel Fernandes
2017-06-10 8:08 ` Joel Fernandes
2017-06-10 13:56 ` Peter Zijlstra
2017-06-11 6:59 ` Joel Fernandes
2017-05-19 6:23 ` [PATCH v2 2/2] sched: Make iowait_boost optional in schedutil Joel Fernandes
2017-05-19 6:50 ` Viresh Kumar
2017-05-19 16:10 ` Joel Fernandes
2017-07-11 19:02 ` Saravana Kannan
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=20170519062344.27692-1-joelaf@google.com \
--to=joelaf@google.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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 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.