From: Patrick Bellasi <patrick.bellasi@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Joel Fernandes <joelaf@google.com>,
Steve Muckle <smuckle@google.com>
Subject: Re: [PATCH 1/3] sched/cpufreq: always consider blocked FAIR utilization
Date: Mon, 14 May 2018 17:33:14 +0100 [thread overview]
Message-ID: <20180514163314.GG30654@e110439-lin> (raw)
In-Reply-To: <CAKfTPtCqoQOiJZktGu-QgCe2A7Cb0N7=eaqqSPN6vy=sKAkQHQ@mail.gmail.com>
On 14-May 11:18, Vincent Guittot wrote:
> On 11 May 2018 at 11:12, Patrick Bellasi <patrick.bellasi@arm.com> wrote:
>
> >>
> >> Do we need a Fixes tag and Cc stable ?
> >
> > Mmm... no sure, I would say that's not a fix.
> >
> > As I say in the changelog above, 8f111bc357aa was doing the correct
> > thing but, since the recent Vincent's commit 31e77c93e432, this is an
> > update worth to have, since now we can trust the decay of blocked
> > utilization.
> >
> > Regarding stable, well... if Vincent patches are not going to be
> > considered for stable, then we should not consider this too, do we?
>
> commit 31e77c93e432 is not for stable so this patch should not go too
Right, will not add stable in cc.
Thanks
--
#include <best/regards.h>
Patrick Bellasi
next prev parent reply other threads:[~2018-05-14 16:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:05 [PATCH 0/3] Improve schedutil integration for FAIR tasks Patrick Bellasi
2018-05-10 15:05 ` [PATCH 1/3] sched/cpufreq: always consider blocked FAIR utilization Patrick Bellasi
2018-05-11 5:44 ` Viresh Kumar
2018-05-11 9:12 ` Patrick Bellasi
2018-05-14 9:18 ` Vincent Guittot
2018-05-14 16:33 ` Patrick Bellasi [this message]
2018-05-10 15:05 ` [PATCH 2/3] sched/fair: util_est: update before schedutil Patrick Bellasi
2018-05-10 15:34 ` Peter Zijlstra
2018-05-11 5:44 ` Viresh Kumar
2018-05-11 8:41 ` Patrick Bellasi
2018-05-10 15:05 ` [PATCH 3/3] sched/fair: schedutil: explicit update only when required Patrick Bellasi
2018-05-10 16:15 ` Peter Zijlstra
2018-05-10 16:54 ` Patrick Bellasi
2018-05-11 5:43 ` Viresh Kumar
2018-05-11 8:42 ` Patrick Bellasi
2018-05-13 6:04 ` Joel Fernandes
2018-05-13 6:25 ` Joel Fernandes
2018-05-14 16:32 ` Patrick Bellasi
2018-05-15 10:19 ` Vincent Guittot
2018-05-15 14:53 ` Patrick Bellasi
2018-05-15 16:53 ` Peter Zijlstra
2018-05-15 17:25 ` Patrick Bellasi
2018-05-16 7:13 ` Vincent Guittot
2018-05-16 7:12 ` Vincent Guittot
2018-05-16 10:45 ` Patrick Bellasi
2018-05-17 15:17 ` Joel Fernandes
2018-05-24 13:42 ` Patrick Bellasi
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=20180514163314.GG30654@e110439-lin \
--to=patrick.bellasi@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.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=rafael.j.wysocki@intel.com \
--cc=smuckle@google.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