From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Julien Desfossez <jdesfossez@efficios.com>,
daolivei <daolivei@redhat.com>, bristot <bristot@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Pulling away from the tracing ABI quicksands
Date: Thu, 29 Jun 2017 22:48:18 -0400 [thread overview]
Message-ID: <20170629224818.0034823e@gandalf.local.home> (raw)
In-Reply-To: <CA+55aFxFLvX62SyOC9qyVwEQXH8J224Fe03tvy624AUx0U2fRQ@mail.gmail.com>
On Thu, 29 Jun 2017 19:34:53 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Oh, I thought it worked outside of perf already. My bad. I'm actually
> surprised it doesn't interact with ftrace, since it seems like the
> perfect use case.
Agreed. I need to push that up in priority in my todo list.
Getting ebpf functionality into tracing could also help filtering and
such, which is still done with tree logic.
Anyway, I would like to get people together in discussing some of these
enhancements at ksummit as well. How to load ebpf into ftrace is another
ABI issue that we need to do right, otherwise that could bite us years
from now.
-- Steve
next prev parent reply other threads:[~2017-06-30 2:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 21:20 Mathieu Desnoyers
2017-06-29 23:55 ` 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 [this message]
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=20170629224818.0034823e@gandalf.local.home \
--to=rostedt@goodmis.org \
--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 \
--cc=torvalds@linux-foundation.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