From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>, juri.lelli@arm.com
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
shilpa.bhat@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V4 0/7] cpufreq: Locking fixes and cleanups
Date: Tue, 9 Feb 2016 09:16:12 +0530 [thread overview]
Message-ID: <cover.1454988792.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
These are rest of the patches that fix some more locking issues with
policy->rwsem and do some minor optimization/cleanups.
These were part of the 13 patch series which was sent earlier. The last
patch is new, and does what I suggested to one of your commits.
V3->V4:
- Reordered all the patches and created a new series.
- s/global/common for common tunables
- One new patch
@Juri/Shilpa: I have added your Tested-by for the first 6 patches,
please let me know if you don't want to add that.
Viresh Kumar (7):
cpufreq: Merge cpufreq_offline_prepare/finish routines
cpufreq: Call __cpufreq_governor() with policy->rwsem held
cpufreq: Remove cpufreq_governor_lock
cpufreq: governor: Move common sysfs tunables to cpufreq_governor.c
cpufreq: governor: No need to manage state machine now
cpufreq: conservative: Update sample_delay_ns immediately
cpufreq: ondemand: Rearrange od_dbs_timer() to void updating delay
drivers/cpufreq/cpufreq.c | 93 +++++++++---------
drivers/cpufreq/cpufreq_conservative.c | 80 +++-------------
drivers/cpufreq/cpufreq_governor.c | 170 ++++++++++++++++++++++++++++-----
drivers/cpufreq/cpufreq_governor.h | 16 +++-
drivers/cpufreq/cpufreq_ondemand.c | 153 +++++------------------------
5 files changed, 240 insertions(+), 272 deletions(-)
--
2.7.1.370.gb2aa7f8
next reply other threads:[~2016-02-09 3:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 3:46 Viresh Kumar [this message]
2016-02-09 3:46 ` [PATCH V4 1/7] cpufreq: Merge cpufreq_offline_prepare/finish routines Viresh Kumar
2016-02-11 0:59 ` Rafael J. Wysocki
2016-02-11 1:15 ` Rafael J. Wysocki
2016-02-11 11:46 ` Viresh Kumar
2016-02-09 3:46 ` [PATCH V4 2/7] cpufreq: Call __cpufreq_governor() with policy->rwsem held Viresh Kumar
2016-02-11 9:48 ` Rafael J. Wysocki
2016-02-11 11:52 ` Viresh Kumar
2016-02-09 3:46 ` [PATCH V4 3/7] cpufreq: Remove cpufreq_governor_lock Viresh Kumar
2016-02-11 9:53 ` Rafael J. Wysocki
2016-02-09 3:46 ` [PATCH V4 4/7] cpufreq: governor: Move common sysfs tunables to cpufreq_governor.c Viresh Kumar
2016-02-10 0:26 ` Rafael J. Wysocki
2016-02-10 7:00 ` [PATCH V5 1/3] cpufreq: governor: No need to manage state machine now Viresh Kumar
2016-02-10 7:00 ` [PATCH V5 2/3] cpufreq: conservative: Update sample_delay_ns immediately Viresh Kumar
2016-02-10 7:00 ` [PATCH V5 3/3] cpufreq: ondemand: Rearrange od_dbs_timer() to avoid updating delay Viresh Kumar
2016-02-11 9:58 ` [PATCH V5 1/3] cpufreq: governor: No need to manage state machine now Rafael J. Wysocki
2016-02-09 3:46 ` [PATCH V4 5/7] " Viresh Kumar
2016-02-10 0:36 ` Rafael J. Wysocki
2016-02-10 5:36 ` Viresh Kumar
2016-02-09 3:46 ` [PATCH V4 6/7] cpufreq: conservative: Update sample_delay_ns immediately Viresh Kumar
2016-02-09 3:46 ` [PATCH V4 7/7] cpufreq: ondemand: Rearrange od_dbs_timer() to void updating delay Viresh Kumar
2016-02-10 0:28 ` Rafael J. Wysocki
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.1454988792.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=juri.lelli@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shilpa.bhat@linux.vnet.ibm.com \
/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).