From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Julien Desfossez <jdesfossez@efficios.com>,
daolivei <daolivei@redhat.com>, bristot <bristot@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: [Ksummit-discuss] [TECH TOPIC] Pulling away from the tracing ABI quicksands
Date: Thu, 29 Jun 2017 21:20:54 +0000 (UTC) [thread overview]
Message-ID: <152520246.5707.1498771254819.JavaMail.zimbra@efficios.com> (raw)
Our attempts at extending the Linux scheduler Tracepoints [1,2,3] to cover sched
rt and deadline policies went fairly well until we reached the point where
we had to extend the tracing ABI exposed to user-space by Ftrace through the
DebugFS tracing sub-directory. We aim to expose more accurate and complete
scheduler information (based on the scheduling class), and eventually deprecate
implementation-specific fields that should never have been exposed to user-space
in the first place.
Example of problems we are facing:
* Humans on the receiving end of a kernel ABI
Should we limit the design of kernel ABIs based on their direct
use by humans through echo and redirections, or can we aim design
of those interfaces at scripts and user-space programs/libraries ?
A simple and extensible kernel ABI is rarely an easy to use end-user
interface.
* How can we deprecate, remove, or re-purpose a field in an
event ? For instance, the "prio" field in the scheduler
instrumentation is an internal implementation detail.
Perhaps it would be good to use the opportunity to meet at the
Kernel Summit and discuss this issue.
Thanks,
Mathieu and Julien
[1] [RFC PATCH 5/6] tracing: extend scheduling tracepoints
http://lkml.kernel.org/r/1474060148-13171-5-git-send-email-jdesfossez@efficios.com
[2] [RFC PATCH v2 0/5] Additional scheduling information in tracepoints
http://lkml.kernel.org/r/1474649375-28056-1-git-send-email-jdesfossez@efficios.com
[3] [RFC PATCH v3 0/2] Extend scheduling tracepoints
http://lkml.kernel.org/r/1484327993-5036-1-git-send-email-jdesfossez@efficios.com
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2017-06-29 21:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 21:20 Mathieu Desnoyers [this message]
2017-06-29 23:55 ` [Ksummit-discuss] [TECH TOPIC] Pulling away from the tracing ABI quicksands Steven Rostedt
2017-06-30 0:03 ` Linus Torvalds
2017-06-30 0:32 ` Steven Rostedt
2017-06-30 0:41 ` Linus Torvalds
2017-06-30 0:59 ` Steven Rostedt
2017-06-30 0:52 ` Steven Rostedt
2017-06-30 1:00 ` Linus Torvalds
2017-06-30 1:16 ` Steven Rostedt
2017-06-30 1:27 ` Steven Rostedt
2017-06-30 1:51 ` Linus Torvalds
2017-06-30 2:12 ` Steven Rostedt
2017-06-30 2:34 ` Linus Torvalds
2017-06-30 2:48 ` Steven Rostedt
2017-06-30 2:58 ` Alexei Starovoitov
2017-06-30 3:02 ` Steven Rostedt
2017-06-30 3:20 ` Steven Rostedt
2017-07-27 14:35 ` Mathieu Desnoyers
2017-07-27 15:57 ` Steven Rostedt
2017-06-30 18:24 ` Josef Bacik
2017-06-30 18:29 ` Steven Rostedt
2017-06-30 18:30 ` Steven Rostedt
2017-06-30 18:37 ` Josef Bacik
2017-07-06 19:10 ` Steven Rostedt
2017-07-21 21:45 ` Mathieu Desnoyers
2017-07-21 23:15 ` James Bottomley
2017-07-22 2:18 ` Steven Rostedt
2017-07-23 16:24 ` Josef Bacik
2017-07-23 21:25 ` Steven Rostedt
2017-07-04 14:51 ` Peter Zijlstra
2017-06-30 1:38 ` Linus Torvalds
2017-06-30 1:45 ` Steven Rostedt
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=152520246.5707.1498771254819.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=bristot@redhat.com \
--cc=daolivei@redhat.com \
--cc=jdesfossez@efficios.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).