linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <Juri.Lelli@arm.com>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	patrick.bellasi@arm.com, john.ettedgui@gmail.com,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Joel Fernandes <joelaf@google.com>,
	Morten Rasmussen <morten.rasmussen@arm.com>
Subject: [PATCH 0/3] cpufreq: schedutil: Fix 4.12 regressions
Date: Fri,  9 Jun 2017 15:45:53 +0530	[thread overview]
Message-ID: <cover.1497002895.git.viresh.kumar@linaro.org> (raw)

Hi Rafael,

I have identified some regressions with the schedutil governor which
happen due to one of your patches that got merged in 4.12-rc1.

This series fixes all the drivers which provide a ->target_index()
callback but doesn't fix the drivers which provide ->target() callback.

Such platforms need to implement the ->resolve_freq() callback in order
to get this fixed and I only had hardware for testing intel_pstate,
which I fixed in this series.

I am wondering if there is another way to fix this issue (than what I
tried) or if we should revert the offending commit (39b64aa1c007) and
look for other solutions.

Anyway, this series has the necessary patches to fix it.

Viresh Kumar (3):
  cpufreq: schedutil: Restore cached_raw_freq behavior
  cpufreq: schedutil: Fix selection algorithm while reducing frequency
  cpufreq: intel_pstate: Provide resolve_freq() to fix regression

 drivers/cpufreq/intel_pstate.c   | 14 +++++++++++++
 kernel/sched/cpufreq_schedutil.c | 45 +++++++++++++++++++++++++++++++++-------
 2 files changed, 52 insertions(+), 7 deletions(-)

-- 
2.13.0.70.g6367777092d9

             reply	other threads:[~2017-06-09 10:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 10:15 Viresh Kumar [this message]
2017-06-09 10:15 ` [PATCH 1/3] cpufreq: schedutil: Restore cached_raw_freq behavior Viresh Kumar
2017-06-09 10:15 ` [PATCH 2/3] cpufreq: schedutil: Fix selection algorithm while reducing frequency Viresh Kumar
2017-06-10  9:11   ` Joel Fernandes
2017-06-11  6:21     ` Joel Fernandes
2017-06-12  3:44       ` Viresh Kumar
2017-06-12 12:33         ` Rafael J. Wysocki
2017-06-09 10:15 ` [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression Viresh Kumar
2017-06-10  9:26   ` Joel Fernandes
2017-06-12  3:41     ` Viresh Kumar
2017-06-09 12:24 ` [PATCH 0/3] cpufreq: schedutil: Fix 4.12 regressions Rafael J. Wysocki
2017-06-09 12:32   ` Viresh Kumar
2017-06-09 13:25     ` 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.1497002895.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=Juri.Lelli@arm.com \
    --cc=joelaf@google.com \
    --cc=john.ettedgui@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=patrick.bellasi@arm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.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).