From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Juri Lelli <Juri.Lelli@arm.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
joelaf@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: schedutil: Update last_update from sugov_set_iowait_boost()
Date: Wed, 19 Jul 2017 00:16:13 +0200 [thread overview]
Message-ID: <9392750.bmStGLhEbp@aspire.rjw.lan> (raw)
In-Reply-To: <20170718113552.v7fzhghp6oxwfoq4@e106622-lin>
On Tuesday, July 18, 2017 12:35:52 PM Juri Lelli wrote:
> On 18/07/17 16:55, Viresh Kumar wrote:
> > On 18-07-17, 12:20, Juri Lelli wrote:
> > > Hi Viresh,
> > >
> > > On 18/07/17 10:24, Viresh Kumar wrote:
>
> [...]
>
> > >
> > > It actually belongs here, IMHO. We update other fields (util, max,
> > > flags)
> >
> > Yeah, because they have bigger roles and aren't specific to iowait
> > boost.
> >
> > > before looking at iowait. Why hiding the time update into a
> > > function dealing with only one of such fields?
> >
> > But last_update is very much specific to iowait_boost only and so it
> > should be updated from sugov_set_iowait_boost() IMHO.
> >
>
> Huh, I see you point. However, I'm using it also to deal with stale CFS
> util values in my patches [1]. Sure, not mainline yet, but I guess I'll
> have to sort of revert your proposed change for my next version. Or
> think of a better idea. :)
Yes, so I'd prefer to prioritize your patches.
The patch from Viresh is purely cosmetic AFAICS and it really can wait.
Thanks,
Rafael
prev parent reply other threads:[~2017-07-18 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 4:54 Viresh Kumar
2017-07-18 11:20 ` Juri Lelli
2017-07-18 11:25 ` Viresh Kumar
2017-07-18 11:35 ` Juri Lelli
2017-07-18 22:16 ` Rafael J. Wysocki [this message]
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=9392750.bmStGLhEbp@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Juri.Lelli@arm.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®