From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: [PATCH V2 0/3] Tracepoints for deadline scheduler
Date: Mon, 28 Mar 2016 13:50:48 -0300 [thread overview]
Message-ID: <cover.1459182044.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.
Changes since v1:
Cleanup in the sched:sched_deadline_yield tracepoint
Fix compilantion warning on Intel 32 bits
Daniel Bristot de Oliveira (2):
sched: Move deadline container_of() helper functions into sched.h
sched/deadline: Tracepoints for deadline scheduler
Steven Rostedt (Red Hat) (1):
tracing: Add __print_ns_to_secs() and __print_ns_without_secs()
helpers
include/trace/events/sched.h | 88 ++++++++++++++++++++++++++++++++++++++++++++
include/trace/trace_events.h | 25 +++++++++++++
kernel/sched/deadline.c | 26 ++++---------
kernel/sched/sched.h | 18 +++++++++
4 files changed, 139 insertions(+), 18 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-28 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 16:50 Daniel Bristot de Oliveira [this message]
2016-03-28 16:50 ` [PATCH V2 1/3] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers Daniel Bristot de Oliveira
2016-03-28 16:50 ` [PATCH V2 2/3] sched: Move deadline container_of() helper functions into sched.h Daniel Bristot de Oliveira
2016-03-28 16:50 ` [PATCH V2 3/3] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-03-29 15:16 ` Peter Zijlstra
2016-03-29 15:57 ` Steven Rostedt
2016-03-29 16:04 ` Peter Zijlstra
2016-03-29 17:10 ` Steven Rostedt
2016-03-29 20:11 ` Peter Zijlstra
2016-03-29 20:29 ` Steven Rostedt
2016-03-29 20:46 ` Peter Zijlstra
2016-03-29 20:57 ` Daniel Bristot de Oliveira
2016-03-29 21:03 ` Peter Zijlstra
2016-03-29 21:49 ` Steven Rostedt
2016-03-29 17:37 ` Daniel Bristot de Oliveira
2016-03-29 18:10 ` Steven Rostedt
2016-03-29 16:10 ` Daniel Bristot de Oliveira
2016-03-29 17:13 ` Steven Rostedt
2016-03-29 19:12 ` Daniel Bristot de Oliveira
2016-03-29 19:25 ` Steven Rostedt
2016-03-31 5:19 ` Juri Lelli
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.1459182044.git.bristot@redhat.com \
--to=bristot@redhat.com \
--cc=acme@redhat.com \
--cc=juri.lelli@arm.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).