From: Juri Lelli <juri.lelli@redhat.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
dietmar.eggemann@arm.com, morten.rasmussen@arm.com,
tkjos@android.com, joelaf@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] sched: cpufreq: Keep track of cpufreq utilization update flags
Date: Wed, 20 Dec 2017 18:27:17 +0100 [thread overview]
Message-ID: <20171220172717.GB22246@localhost.localdomain> (raw)
In-Reply-To: <5156588.pkDhmtr2np@aspire.rjw.lan>
On 20/12/17 15:47, Rafael J. Wysocki wrote:
> On Wednesday, December 20, 2017 2:28:26 PM CET Peter Zijlstra wrote:
> > On Wed, Dec 20, 2017 at 12:55:46PM +0000, Patrick Bellasi wrote:
> > > On 20-Dec 09:31, Peter Zijlstra wrote:
> >
> > > > Didn't juri have patches to make DL do something sane? But yes, I think
> > > > those flags are part of the problem.
> > >
> > > He recently reposted them here:
> > >
> > > https://lkml.kernel.org/r/20171204102325.5110-1-juri.lelli@redhat.com
> >
> > Yeah, just found them and actually munged them into my queue; did all
> > the modifications you suggested too. Lets see if it comes apart.
>
> Good, because I think that the Juri's patches should go in first.
>
Thanks Peter for taking the patches. I was actually waiting for the flag
thing to be resolved to post again. :/
Anyway, let us know how it goes and if I need to make further changes.
Best,
- Juri
next prev parent reply other threads:[~2017-12-20 17:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 9:53 [PATCH 0/4] sched: cpufreq: Track util update flags Viresh Kumar
2017-12-13 9:53 ` [PATCH 1/4] cpufreq: schedutil: Initialize sg_cpu->flags to 0 Viresh Kumar
2017-12-13 11:13 ` Juri Lelli
2017-12-13 11:22 ` Viresh Kumar
2018-01-10 12:15 ` [tip:sched/core] sched/cpufreq: " tip-bot for Viresh Kumar
2017-12-13 9:53 ` [PATCH 2/4] sched: cpufreq: Keep track of cpufreq utilization update flags Viresh Kumar
2017-12-13 11:26 ` Juri Lelli
2017-12-13 11:29 ` Viresh Kumar
2017-12-16 16:40 ` Rafael J. Wysocki
2017-12-16 16:47 ` Viresh Kumar
2017-12-17 0:19 ` Rafael J. Wysocki
2017-12-18 4:59 ` Viresh Kumar
2017-12-18 11:35 ` Rafael J. Wysocki
2017-12-18 11:59 ` Viresh Kumar
2017-12-18 12:14 ` Patrick Bellasi
2017-12-19 3:12 ` Viresh Kumar
2017-12-19 3:18 ` Joel Fernandes
2017-12-19 3:22 ` Viresh Kumar
2017-12-19 3:26 ` Viresh Kumar
2017-12-19 3:30 ` Joel Fernandes
2017-12-19 3:41 ` Viresh Kumar
2017-12-19 10:44 ` Rafael J. Wysocki
2017-12-18 17:34 ` Rafael J. Wysocki
2017-12-19 19:25 ` Peter Zijlstra
2017-12-20 4:04 ` Viresh Kumar
2017-12-20 8:31 ` Peter Zijlstra
2017-12-20 8:48 ` Viresh Kumar
2017-12-20 9:17 ` Peter Zijlstra
2017-12-20 12:55 ` Patrick Bellasi
2017-12-20 13:28 ` Peter Zijlstra
2017-12-20 14:31 ` Patrick Bellasi
2017-12-20 14:52 ` Rafael J. Wysocki
2017-12-20 15:01 ` Patrick Bellasi
2017-12-20 14:47 ` Rafael J. Wysocki
2017-12-20 14:51 ` Peter Zijlstra
2017-12-20 17:27 ` Juri Lelli [this message]
2017-12-20 18:17 ` Peter Zijlstra
2017-12-13 9:53 ` [PATCH 3/4] cpufreq: schedutil: Don't pass flags to sugov_set_iowait_boost() Viresh Kumar
2017-12-13 11:28 ` Juri Lelli
2018-01-10 12:15 ` [tip:sched/core] sched/cpufreq: " tip-bot for Viresh Kumar
2017-12-13 9:53 ` [PATCH 4/4] cpufreq: schedutil: Don't call sugov_get_util() unnecessarily Viresh Kumar
2017-12-13 11:34 ` Juri Lelli
2017-12-13 12:02 ` Viresh Kumar
2017-12-19 3:26 ` Joel Fernandes
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=20171220172717.GB22246@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=rjw@rjwysocki.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.