From: Qais Yousef <qais.yousef@arm.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: 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: Mon, 17 Jun 2019 13:51:23 +0100 [thread overview]
Message-ID: <20190617125122.ph4wb7mcvfjwpdce@e107158-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190604111459.2862-1-qais.yousef@arm.com>
Hi Peter
On 06/04/19 12:14, Qais Yousef wrote:
> Changes in v3:
> - Split pelt_rq TP into pelt_cfs, pelt_rq, pelt_dl and pelt_irq
> - Replace the fatty preprocessing wrappers with exported helper
> functions to access data in unexported structures.
> - Remove the now unnecessary headers that were introduced in the
> previous versions.
> - Postfix the tracepoints with '_tp' to make them standout more in the
> code as bare tracepoints with no events associated.
> - Updated the example module in [2]
> - It demonstrates now how to convert the tracepoints into trace
> events that extend the sched events subsystem in tracefs.
Does this look okay now? If you have further comments please let me know so
I can address them in time in hope it'd make it to the next merge window.
Thanks
--
Qais Yousef
next prev parent reply other threads:[~2019-06-17 12:51 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
2019-06-17 12:51 ` Qais Yousef [this message]
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=20190617125122.ph4wb7mcvfjwpdce@e107158-lin.cambridge.arm.com \
--to=qais.yousef@arm.com \
--cc=bigeasy@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--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).