From: Viresh Kumar <viresh.kumar@linaro.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: 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>,
Joel Fernandes <joelaf@google.com>,
Steve Muckle <smuckle@google.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH v2] cpufreq/schedutil: Cleanup, document and fix iowait boost
Date: Wed, 11 Apr 2018 20:14:56 +0530 [thread overview]
Message-ID: <20180411144456.GP7671@vireshk-i7> (raw)
In-Reply-To: <20180411104824.GN14248@e110439-lin>
On 11-04-18, 11:48, Patrick Bellasi wrote:
> On 11-Apr 10:07, Viresh Kumar wrote:
> > On 10-04-18, 16:59, Patrick Bellasi wrote:
> > The above part should be a different patch with this:
> >
> > Fixes: a5a0809bc58e ("cpufreq: schedutil: Make iowait boost more energy efficient")
>
> You mean to split out on a separate patch the fix for the iowait boost
> on per-cpu policies?
Right.
> > And the rest is just code rearrangement. And as Peter said, we better
> > have a routine to clear boost values on delta > TICK_NSEC.
>
> Right, already commented in reply to Peter. I'll split in two patches:
> one for documentation and code re-organization and a second one for
> the fix to the issue you pointed out.
Thanks.
--
viresh
prev parent reply other threads:[~2018-04-11 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:59 [PATCH v2] cpufreq/schedutil: Cleanup, document and fix iowait boost Patrick Bellasi
2018-04-10 19:37 ` Peter Zijlstra
2018-04-11 10:44 ` Patrick Bellasi
2018-04-11 10:58 ` Peter Zijlstra
2018-04-11 14:39 ` Patrick Bellasi
2018-04-11 14:54 ` Viresh Kumar
2018-04-11 4:37 ` Viresh Kumar
2018-04-11 10:48 ` Patrick Bellasi
2018-04-11 14:44 ` Viresh Kumar [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=20180411144456.GP7671@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=smuckle@google.com \
/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.