From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/6] cpufreq: governor: replace per-cpu delayed work with timers
Date: Thu, 29 Oct 2015 17:57:19 +0530 [thread overview]
Message-ID: <cover.1446121217.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
As suggested by you yesterday, I have updated the governor core to keep
per-cpu timers and a shared work for the entire policy.
More details are present in the changelogs, hope they are somewhat
better this time.
I have tested it with the test-suite, that I created sometime back while
fixing locking issues in governors.. Tried all kind of stuff in parallel
that could have broken it (those are the testcases that separate people
reported over time, around governors). It works fine.
The first one is a bug fix really, which I noticed today only :), next
three are minor cleanups to prepare for the big change. Fourth one is
the main patch that does the conversion and the final one is
cherry-picked from the last series as that was still relevant.
This is rebased over: pm/bleeding-edge + "[PATCH V4] cpufreq: governor:
Quit work-handlers early if governor is stopped", which I sent
separately this morning with the changelog you suggested.
Please see if this meets your expectations or not :)
Viresh Kumar (6):
cpufreq: ondemand: Update sampling rate only for concerned policies
cpufreq: ondemand: Work is guaranteed to be pending
cpufreq: governor: Pass policy as argument to ->gov_dbs_timer()
cpufreq: governor: initialize/destroy timer_mutex with 'shared'
cpufreq: governor: replace per-cpu delayed work with timers
cpufreq: ondemand: update update_sampling_rate() to make it more
efficient
drivers/cpufreq/cpufreq_conservative.c | 6 +-
drivers/cpufreq/cpufreq_governor.c | 145 +++++++++++++++++++--------------
drivers/cpufreq/cpufreq_governor.h | 23 ++++--
drivers/cpufreq/cpufreq_ondemand.c | 66 ++++++++++-----
4 files changed, 147 insertions(+), 93 deletions(-)
--
2.6.2.198.g614a2ac
next reply other threads:[~2015-10-29 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 12:27 Viresh Kumar [this message]
2015-10-29 12:27 ` [PATCH 1/6] cpufreq: ondemand: Update sampling rate only for concerned policies Viresh Kumar
2015-12-03 2:16 ` Rafael J. Wysocki
2015-10-29 12:27 ` [PATCH 2/6] cpufreq: ondemand: Work is guaranteed to be pending Viresh Kumar
2015-10-29 12:27 ` [PATCH 3/6] cpufreq: governor: Pass policy as argument to ->gov_dbs_timer() Viresh Kumar
2015-10-29 12:27 ` [PATCH 4/6] cpufreq: governor: initialize/destroy timer_mutex with 'shared' Viresh Kumar
2015-10-29 12:27 ` [PATCH 5/6] cpufreq: governor: replace per-cpu delayed work with timers Viresh Kumar
2015-10-30 20:46 ` Ashwin Chaugule
2015-10-31 2:36 ` Viresh Kumar
2015-11-03 19:01 ` Ashwin Chaugule
2015-11-30 12:05 ` Lucas Stach
2015-11-30 13:35 ` Viresh Kumar
2015-10-29 12:27 ` [PATCH 6/6] cpufreq: ondemand: update update_sampling_rate() to make it more efficient Viresh Kumar
2015-11-27 5:53 ` [PATCH 0/6] cpufreq: governor: replace per-cpu delayed work with timers Viresh Kumar
2015-12-03 2:22 ` 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.1446121217.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).