From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: vincent.donnefort@arm.com, mingo@redhat.com,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org,
patrick.bellasi@matbug.net, dietmar.eggemann@arm.com,
qais.yousef@arm.com
Subject: Re: [PATCH] sched/debug: Add new tracepoints to track util_est
Date: Wed, 3 Jun 2020 14:15:30 +0200 [thread overview]
Message-ID: <20200603121530.GB2570@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <jhjlfl4icdx.mognet@arm.com>
On Wed, Jun 03, 2020 at 01:04:26PM +0100, Valentin Schneider wrote:
>
> On 27/05/20 17:39, vincent.donnefort@arm.com wrote:
> > From: Vincent Donnefort <vincent.donnefort@arm.com>
> >
> > The util_est signals are key elements for EAS task placement and
> > frequency selection. Having tracepoints to track these signals enables
> > load-tracking and schedutil testing and/or debugging by a toolkit.
> >
> > Signed-off-by: Vincent Donnefort <vincent.donnefort@arm.com>
> >
>
> To put it more bluntly, we can't really do task placement / load tracking
> testing if util_est is enabled (which reminds me we may want to get rid of
> the SCHED_FEAT at some point, it's been default on since ~v4.17), since
> there can be noticeable gaps between util_avg and util_est.
>
> Reviewed-by: Valentin Schneider <valentin.schneider@arm.com>
Thanks!
next prev parent reply other threads:[~2020-06-03 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 16:39 [PATCH] sched/debug: Add new tracepoints to track util_est vincent.donnefort
2020-06-03 12:04 ` Valentin Schneider
2020-06-03 12:15 ` Peter Zijlstra [this message]
2020-06-16 12:21 ` [tip: sched/core] " tip-bot2 for Vincent Donnefort
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=20200603121530.GB2570@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=qais.yousef@arm.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.donnefort@arm.com \
--cc=vincent.guittot@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;
as well as URLs for NNTP newsgroup(s).