From: Peter Zijlstra <peterz@infradead.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Joel Fernandes <joelaf@google.com>,
Steve Muckle <smuckle@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>
Subject: Re: [PATCH] sched/fair: schedutil: update only with all info available
Date: Wed, 11 Apr 2018 16:53:16 +0200 [thread overview]
Message-ID: <20180411145316.GJ4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180406172835.20078-1-patrick.bellasi@arm.com>
On Fri, Apr 06, 2018 at 06:28:35PM +0100, Patrick Bellasi wrote:
> is maintained although there are not actual usages so far in mainline
> for this hint... do we really need it?
There were intel_pstate patches that I expected to have shown up
already, and I meant to have a look at sugov, except I got side-tracked
again :/
prev parent reply other threads:[~2018-04-11 14:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 17:28 [PATCH] sched/fair: schedutil: update only with all info available Patrick Bellasi
2018-04-06 23:48 ` Joel Fernandes
2018-04-10 11:44 ` Patrick Bellasi
2018-04-09 8:51 ` Vincent Guittot
2018-04-10 11:04 ` Patrick Bellasi
2018-04-11 6:57 ` Vincent Guittot
2018-04-11 10:15 ` Patrick Bellasi
2018-04-11 11:56 ` Vincent Guittot
2018-04-11 14:33 ` Patrick Bellasi
2018-04-11 21:34 ` Joel Fernandes
2018-04-12 7:01 ` Vincent Guittot
2018-04-12 18:06 ` Joel Fernandes
2018-04-11 15:14 ` Peter Zijlstra
2018-04-11 15:29 ` Vincent Guittot
2018-04-11 15:37 ` Peter Zijlstra
2018-04-11 15:41 ` Vincent Guittot
2018-04-11 16:00 ` Peter Zijlstra
2018-04-11 16:10 ` Vincent Guittot
2018-04-11 16:15 ` Peter Zijlstra
2018-04-11 16:51 ` Vincent Guittot
2018-04-26 11:15 ` Patrick Bellasi
2018-04-26 11:52 ` Peter Zijlstra
2018-04-11 7:57 ` Vincent Guittot
2018-04-11 9:27 ` Patrick Bellasi
2018-04-11 14:53 ` Peter Zijlstra [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=20180411145316.GJ4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.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=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--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