From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: [PATCH 0/4] Tracepoints for deadline scheduler
Date: Mon, 22 Feb 2016 14:08:18 -0300 [thread overview]
Message-ID: <cover.1456157869.git.bristot@redhat.com> (raw)
Deadline tasks behave differently of other tasks because deadline
task's also depend on their period, deadline and runtime.
Hence, the well known sched:sched_wakeup and sched:sched_switch
tracepoints are not always enough to precisely explain the behavior of a
deadline task with respect to the task's period, deadline and runtime
consumption.
This patch series implements tracepoints for the following deadline
scheduler points of interest:
- sched:sched_deadline_replenish: Informs the periodic runtime
replenishment of a deadline task.
- sched:sched_deadline_yield: Informs that a deadline task called
sched_yield(), and will wait for the next period.
- sched:sched_deadline_throttle: Informs that a task consumed all its
available runtime and was throttled.
- sched:sched_deadline_block: Informs that a deadline task went to sleep
waiting to be awakened by another task.
Daniel Bristot de Oliveira (3):
sched: Move deadline container_of() helper functions into sched.h
sched/deadline: Tracepoints for deadline scheduler
tools lib traceevent: Implements '%' operation
Steven Rostedt (Red Hat) (1):
tracing: Add __print_ns_to_secs() and __print_ns_without_secs()
helpers
include/trace/events/sched.h | 87 ++++++++++++++++++++++++++++++++++++++
include/trace/trace_events.h | 25 +++++++++++
kernel/sched/deadline.c | 34 +++++++--------
kernel/sched/sched.h | 18 ++++++++
tools/lib/traceevent/event-parse.c | 4 ++
5 files changed, 149 insertions(+), 19 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-22 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:08 Daniel Bristot de Oliveira [this message]
2016-02-22 17:08 ` [PATCH 1/4] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers Daniel Bristot de Oliveira
2016-02-22 17:08 ` [PATCH 2/4] sched: Move deadline container_of() helper functions into sched.h Daniel Bristot de Oliveira
2016-02-22 17:08 ` [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-02-22 17:32 ` Peter Zijlstra
2016-02-22 17:48 ` Steven Rostedt
2016-02-22 20:11 ` Daniel Bristot de Oliveira
2016-02-22 21:30 ` Peter Zijlstra
2016-02-22 22:30 ` Steven Rostedt
2016-02-23 10:40 ` Juri Lelli
2016-02-23 10:44 ` Peter Zijlstra
2016-02-23 13:10 ` Steven Rostedt
2016-02-24 8:48 ` Ingo Molnar
2016-02-23 14:27 ` Peter Zijlstra
2016-02-23 16:19 ` Daniel Bristot de Oliveira
2016-02-24 2:29 ` Daniel Bristot de Oliveira
2016-02-22 17:48 ` kbuild test robot
2016-02-22 17:08 ` [PATCH 4/4] tools lib traceevent: Implements '%' operation Daniel Bristot de Oliveira
2016-02-22 20:23 ` Steven Rostedt
2016-02-23 14:38 ` Arnaldo Carvalho de Melo
2016-02-23 14:44 ` Arnaldo Carvalho de Melo
2016-02-25 5:41 ` [tip:perf/core] tools lib traceevent: Implement " tip-bot for Daniel Bristot de Oliveira
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=cover.1456157869.git.bristot@redhat.com \
--to=bristot@redhat.com \
--cc=acme@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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).