From: Qais Yousef <qais.yousef@arm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Pavankumar Kondeti <pkondeti@codeaurora.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Uwe Kleine-Konig <u.kleine-koenig@pengutronix.de>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Quentin Perret <quentin.perret@arm.com>
Subject: Re: [PATCH v3 0/6] sched: Add new tracepoints required for EAS testing
Date: Wed, 5 Jun 2019 23:33:43 +0100 [thread overview]
Message-ID: <20190605223343.r42pgngvs7myzfke@e107158-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190605061748.GA20661@infradead.org>
On 06/04/19 23:17, Christoph Hellwig wrote:
> > The following patches add the bare minimum tracepoints required to perform EAS
> > testing in Lisa[1].
>
> What is EAS? Whhy is "Lisa" not part of the patch submission?
> submission.
EAS is Energy Aware Scheduling. It was merged in 5.0.
Lisa is a python based testing platform that has dependency on other binaries
like trace-cmd, rt-app, etc. It is not suitable for kernel submission.
Lisa, or any userspace based testing for that matter, requires to know what's
happening inside the scheduler to test its behavior. I don't know know of any
other scheduler centric testing framework. I didn't intend to specify Lisa as
the sole user and reason for these tracepoints, I know others are interested in
these tracepoints in general for anyone who wants to achieve a similar goal of
studying scheduler PELT behavior and how it affects some of the decisions it
makes.
We had a talk in OSPM a couple of weeks ago to cover this topic if you're
interested to learn more
https://www.youtube.com/watch?v=I_MZ9XS3_zc
>
> > It is done in this way because adding new TRACE_EVENTS() is no longer accepted
> > AFAIU.
>
> Huh? We keep adding trace events all the time. And they actually
> are useful because they are testable.
>
> This series on the other hand adds exports not used in tree, which is
> a big no-go.
I see that Peter has already covered this part.
Thanks
--
Qais Yousef
next prev parent reply other threads:[~2019-06-05 22:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:14 [PATCH v3 0/6] sched: Add new tracepoints required for EAS testing Qais Yousef
2019-06-04 11:14 ` [PATCH v3 1/6] sched: autogroup: Make autogroup_path() always available Qais Yousef
2019-06-25 8:24 ` [tip:sched/core] sched/autogroup: " tip-bot for Qais Yousef
2019-06-04 11:14 ` [PATCH v3 2/6] sched: add a new sched_trace_*() helper functions Qais Yousef
2019-06-25 8:25 ` [tip:sched/core] sched/debug: Add " tip-bot for Qais Yousef
2019-06-04 11:14 ` [PATCH v3 3/6] sched: Add new tracepoints to track pelt at rq level Qais Yousef
2019-06-25 8:26 ` [tip:sched/core] sched/debug: Add new tracepoints to track PELT " tip-bot for Qais Yousef
2019-06-04 11:14 ` [PATCH v3 4/6] sched: Add new tracepoint to track pelt at se level Qais Yousef
2019-06-25 8:27 ` [tip:sched/core] sched/debug: Add new tracepoint to track PELT " tip-bot for Qais Yousef
2019-06-04 11:14 ` [PATCH v3 5/6] sched: Add sched_overutilized tracepoint Qais Yousef
2019-06-17 15:50 ` Peter Zijlstra
2019-06-17 16:31 ` Qais Yousef
2019-06-25 8:27 ` [tip:sched/core] sched/debug: " tip-bot for Qais Yousef
2019-06-04 11:14 ` [PATCH v3 6/6] sched: export the newly added tracepoints Qais Yousef
2019-06-25 8:28 ` [tip:sched/core] sched/debug: Export " tip-bot for Qais Yousef
2019-06-05 6:17 ` [PATCH v3 0/6] sched: Add new tracepoints required for EAS testing Christoph Hellwig
2019-06-05 7:22 ` Peter Zijlstra
2019-06-05 22:33 ` Qais Yousef [this message]
2019-06-17 12:51 ` Qais Yousef
2019-06-17 15:55 ` Peter Zijlstra
2019-06-17 16:22 ` Qais Yousef
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=20190605223343.r42pgngvs7myzfke@e107158-lin.cambridge.arm.com \
--to=qais.yousef@arm.com \
--cc=bigeasy@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pkondeti@codeaurora.org \
--cc=quentin.perret@arm.com \
--cc=rostedt@goodmis.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).