From: Juri Lelli <juri.lelli@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Patrick Bellasi <patrick.bellasi@arm.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Todd Kjos <tkjos@android.com>, Joel Fernandes <joelaf@google.com>
Subject: Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter
Date: Tue, 12 Dec 2017 14:38:24 +0100 [thread overview]
Message-ID: <20171212133824.GH4635@localhost.localdomain> (raw)
In-Reply-To: <20171212113727.GO25177@vireshk-i7>
Hi Viresh,
On 12/12/17 17:07, Viresh Kumar wrote:
[...]
> From: Viresh Kumar <viresh.kumar@linaro.org>
> Date: Tue, 12 Dec 2017 15:43:26 +0530
> Subject: [PATCH] sched: Keep track of cpufreq utilization update flags
>
> Currently the schedutil governor overwrites the sg_cpu->flags field on
> every call to the utilization handler. It was pretty good as the initial
> implementation of utilization handlers, there are several drawbacks
> though.
>
> The biggest drawback is that the sg_cpu->flags field doesn't always
> represent the correct type of tasks that are enqueued on a CPU's rq. For
> example, if a fair task is enqueued while a RT or DL task is running, we
> will overwrite the flags with value 0 and that may take the CPU to lower
> OPPs unintentionally. There can be other corner cases as well which we
> aren't aware of currently.
>
> This patch changes the current implementation to keep track of all the
> task types that are currently enqueued to the CPUs rq. There are two
> flags for every scheduling class now, one to set the flag and other one
> to clear it. The flag is set by the scheduling classes from the existing
> set of calls to cpufreq_update_util(), and the flag is cleared when the
> last task of the scheduling class is dequeued. For now, the util update
> handlers return immediately if they were called to clear the flag.
>
> We can add more optimizations over this patch separately.
>
> The last parameter of sugov_set_iowait_boost() is also dropped as the
> function can get it from sg_cpu anyway.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[...]
> @@ -655,7 +669,7 @@ static int sugov_start(struct cpufreq_policy *policy)
> memset(sg_cpu, 0, sizeof(*sg_cpu));
> sg_cpu->cpu = cpu;
> sg_cpu->sg_policy = sg_policy;
> - sg_cpu->flags = SCHED_CPUFREQ_RT;
> + sg_cpu->flags = 0;
> sg_cpu->iowait_boost_max = policy->cpuinfo.max_freq;
> }
Why this change during initialization?
Thanks,
- Juri
next prev parent reply other threads:[~2017-12-12 13:38 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:47 [PATCH v3 0/6] cpufreq: schedutil: fixes for flags updates Patrick Bellasi
2017-11-30 11:47 ` [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter Patrick Bellasi
2017-11-30 13:12 ` Juri Lelli
2017-11-30 15:41 ` Patrick Bellasi
2017-11-30 16:02 ` Juri Lelli
2017-11-30 16:19 ` Patrick Bellasi
2017-11-30 16:45 ` Juri Lelli
2017-12-07 5:01 ` Viresh Kumar
2017-12-07 12:45 ` Patrick Bellasi
2017-12-07 15:55 ` Dietmar Eggemann
2017-12-12 11:37 ` Viresh Kumar
2017-12-12 13:38 ` Juri Lelli [this message]
2017-12-12 14:40 ` Viresh Kumar
2017-12-12 14:56 ` Juri Lelli
2017-12-12 15:18 ` Patrick Bellasi
2017-12-12 15:16 ` Patrick Bellasi
2017-12-13 9:06 ` Viresh Kumar
2017-12-20 14:33 ` Peter Zijlstra
2017-12-20 14:51 ` Patrick Bellasi
2017-11-30 11:47 ` [PATCH v3 2/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks Patrick Bellasi
2017-11-30 13:17 ` Juri Lelli
2017-11-30 15:45 ` Patrick Bellasi
2017-11-30 16:03 ` Juri Lelli
2017-12-07 5:05 ` Viresh Kumar
2017-12-07 14:18 ` Patrick Bellasi
2017-11-30 11:47 ` [PATCH v3 3/6] cpufreq: schedutil: update CFS util only if used Patrick Bellasi
2017-11-30 13:22 ` Juri Lelli
2017-11-30 15:57 ` Patrick Bellasi
2017-12-07 5:15 ` Viresh Kumar
2017-12-07 14:19 ` Patrick Bellasi
2017-12-14 4:45 ` Viresh Kumar
2017-11-30 11:47 ` [PATCH v3 4/6] sched/rt: fast switch to maximum frequency when RT tasks are scheduled Patrick Bellasi
2017-11-30 13:28 ` Juri Lelli
2017-12-06 9:39 ` Vincent Guittot
2017-12-06 11:38 ` Patrick Bellasi
2017-12-06 12:36 ` Vincent Guittot
2017-11-30 11:47 ` [PATCH v3 5/6] cpufreq: schedutil: relax rate-limiting while running RT/DL tasks Patrick Bellasi
2017-11-30 13:36 ` Juri Lelli
2017-11-30 15:54 ` Patrick Bellasi
2017-11-30 16:06 ` Juri Lelli
2017-11-30 11:47 ` [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads Patrick Bellasi
2017-11-30 13:41 ` Juri Lelli
2017-11-30 16:02 ` Patrick Bellasi
2017-11-30 16:12 ` Juri Lelli
2017-11-30 16:42 ` Patrick Bellasi
2017-12-07 9:24 ` Viresh Kumar
2017-12-07 15:47 ` Patrick Bellasi
2017-12-20 15:30 ` [PATCH v3 0/6] cpufreq: schedutil: fixes for flags updates Peter Zijlstra
2017-12-20 15:43 ` Peter Zijlstra
2017-12-21 9:15 ` Viresh Kumar
2017-12-21 10:25 ` Peter Zijlstra
2017-12-21 10:30 ` Viresh Kumar
2017-12-21 10:39 ` Peter Zijlstra
2017-12-21 10:43 ` Viresh Kumar
2017-12-22 8:30 ` Peter Zijlstra
2017-12-20 15:56 ` Peter Zijlstra
2017-12-31 9:43 ` Claudio Scordino
2018-01-02 13:31 ` Claudio Scordino
2017-12-20 17:38 ` Juri Lelli
2017-12-20 18:16 ` Peter Zijlstra
2017-12-22 10:06 ` Peter Zijlstra
2017-12-22 11:02 ` Patrick Bellasi
2017-12-22 11:46 ` Peter Zijlstra
2017-12-22 12:07 ` Juri Lelli
2017-12-22 12:14 ` Patrick Bellasi
2017-12-22 12:22 ` Peter Zijlstra
2017-12-22 12:07 ` Patrick Bellasi
2017-12-22 12:19 ` Peter Zijlstra
2017-12-22 12:27 ` Juri Lelli
2017-12-22 12:38 ` Patrick Bellasi
2017-12-22 12:43 ` Juri Lelli
2017-12-22 12:50 ` Patrick Bellasi
2017-12-22 13:01 ` Juri Lelli
2017-12-22 12:10 ` Peter Zijlstra
2017-12-22 12:25 ` Patrick Bellasi
2017-12-21 7:34 ` Viresh Kumar
2018-02-06 10:55 ` Claudio Scordino
2018-02-06 15:43 ` Patrick Bellasi
2018-02-06 18:14 ` Claudio Scordino
2018-02-06 18:36 ` Patrick Bellasi
2018-02-08 16:14 ` Claudio Scordino
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=20171212133824.GH4635@localhost.localdomain \
--to=juri.lelli@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--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=rafael.j.wysocki@intel.com \
--cc=tkjos@android.com \
--cc=vincent.guittot@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).