From: Julien Desfossez <jdesfossez@efficios.com>
To: peterz@infradead.org, rostedt@goodmis.org, tglx@linutronix.de,
mingo@redhat.com, bristot@redhat.com,
mathieu.desnoyers@efficios.com
Cc: linux-kernel@vger.kernel.org, Julien Desfossez <jdesfossez@efficios.com>
Subject: [RFC PATCH v3 0/2] Extend scheduling tracepoints
Date: Fri, 13 Jan 2017 12:19:51 -0500 [thread overview]
Message-ID: <1484327993-5036-1-git-send-email-jdesfossez@efficios.com> (raw)
This patchset proposes a way to extend the existing scheduling tracepoints. The
intent is to allow to output relevant priority informations based on the
scheduling class of the tasks without breaking the existing tracepoints or
having to handle the various cases in the scheduler code.
The proposed approach is to add the TRACE_EVENT_MAP_COND macro which depends on
an existing TRACE_EVENT, but only writes data into the trace when a condition
is satisfied. This allows to create multiple versions of the same tracepoint
without having to call each of them explicitly from the instrumented code.
This approach is then illustrated with the sched_switch tracepoint, where we
provide a way to output different fields based on the scheduling class of the
next task.
If accepted, this method could be used everywhere the "prio" field is currently
exposed to user-space through traces.
Julien Desfossez (2):
tracing: add TRACE_EVENT_MAP_COND
tracing: add policy-based sched_switch events
include/linux/trace_events.h | 14 +++-
include/linux/tracepoint.h | 6 ++
include/trace/define_trace.h | 6 ++
include/trace/events/sched.h | 192 +++++++++++++++++++++++++++++++++++++++++++
include/trace/perf.h | 24 ++++--
include/trace/trace_events.h | 130 +++++++++++++++++++++++++----
kernel/trace/trace_events.c | 15 +++-
7 files changed, 360 insertions(+), 27 deletions(-)
--
1.9.1
next reply other threads:[~2017-01-13 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:19 Julien Desfossez [this message]
2017-01-13 17:19 ` [RFC PATCH v3 1/2] tracing: add TRACE_EVENT_MAP_COND Julien Desfossez
2017-01-13 17:19 ` [RFC PATCH v3 2/2] tracing: add policy-based sched_switch events Julien Desfossez
2017-02-07 12:23 ` Peter Zijlstra
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=1484327993-5036-1-git-send-email-jdesfossez@efficios.com \
--to=jdesfossez@efficios.com \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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
all inboxes | Powered by JetHome®