public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Redpath <chris.redpath@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3] cpufreq: schedutil: Examine the correct CPU when we update util
Date: Tue, 7 Nov 2017 09:49:58 +0000	[thread overview]
Message-ID: <65a16c84-d25f-26ce-b4cf-5edc3f9b6d32@arm.com> (raw)
In-Reply-To: <20171103154559.GJ4240@vireshk-i7>

Hi Viresh, Rafael,

Without this patch, schedutil is totally broken for us - is
there any chance at all this could go in 4.14 or is it just
too late?

Best Regards,
Chris

On 03/11/17 15:45, Viresh Kumar wrote:
> On 03-11-17, 13:36, Chris Redpath wrote:
>> After
>> 674e75411fc2 ("sched: cpufreq: Allow remote cpufreq callbacks")
>>
>> We stopped always reading utilization for the cpu we are running
>> the governor on, and instead read it for the cpu which we've been
>> told has updated utilization. This is stored in sugov_cpu->cpu.
>>
>> The value is set in sugov_register but we clear it in sugov_start
>> which leads to always looking at the utilization of CPU0 instead
>> of the correct one.
>>
>> Let's fix this by consolidating the initialization code into
>> sugov_start().
>>
>> Fixes: 674e75411fc2 ("sched: cpufreq: Allow remote cpufreq callbacks")
>> Signed-off-by: Chris Redpath <chris.redpath@arm.com>
>> Reviewed-by: Patrick Bellasi <patrick.bellasi@arm.com>
>> Reviewed-by: Brendan Jackman <brendan.jackman@arm.com>
>> 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>
>> ---
>>   kernel/sched/cpufreq_schedutil.c | 6 +-----
>>   1 file changed, 1 insertion(+), 5 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2017-11-07  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 10:54 [PATCH] cpufreq: schedutil: Examine the correct CPU when we update util Chris Redpath
2017-11-02 11:10 ` Viresh Kumar
2017-11-02 11:38   ` [PATCH v2] " Chris Redpath
2017-11-02 11:40     ` Viresh Kumar
2017-11-02 12:06       ` Chris Redpath
2017-11-03  3:40         ` Viresh Kumar
2017-11-03 13:36           ` [PATCH v3] " Chris Redpath
2017-11-03 15:45             ` Viresh Kumar
2017-11-07  9:49               ` Chris Redpath [this message]
2017-11-07  9:59                 ` Viresh Kumar
2017-11-07 10:09                   ` Rafael J. Wysocki
2017-11-07 11:03                     ` Chris Redpath

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=65a16c84-d25f-26ce-b4cf-5edc3f9b6d32@arm.com \
    --to=chris.redpath@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox