From: Josef Bacik <jbacik@fb.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
bristot <bristot@redhat.com>,
Julien Desfossez <jdesfossez@efficios.com>,
Ingo Molnar <mingo@kernel.org>, daolivei <daolivei@redhat.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Pulling away from the tracing ABI quicksands
Date: Fri, 30 Jun 2017 18:37:59 +0000 [thread overview]
Message-ID: <658A3F80-5E48-4EC4-A591-E3783AD3DADC@fb.com> (raw)
In-Reply-To: <20170630143030.305b68a0@gandalf.local.home>
[ I forgot to add Tom to the Cc list. Sending again. ]
On Fri, 30 Jun 2017 14:29:56 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 30 Jun 2017 18:24:12 +0000
> Josef Bacik <jbacik@fb.com> wrote:
>
> > Yup I’ll start bugging people to submit talk proposals, starting with you! I’ll put up my proposal in the next day or two, I think Brendan has something he’s going to talk about. Thanks,
>
> I shouldn't have used the term "talk", as it really is all about
> discussions. In fact, if you need more than one slide, you have too
> many.
>
> That said, I could probably come up with a few things, starting with
> this trace event issue. But it will be pointless if Peter Zijlstra and
> Mathieu are not there.
>
> But having ideas about dynamic fields in tracepoints is always
> interesting. Not to mention talking about Tom Zanussi's latest
> histogram work. It may be pretty much completed, but I would like to
> discuss where we go from there.
>
> One last thing. I don't want to have too many responsibilities, as I'm
> on the LPC program committee and I need to make sure I have time to
> fulfill any action items I'm responsible for during the conference.
>
Yeah plumbers is a weird venue for tracing, I always hope that we are going to have people like Brendan or other sysadmin-y people show up and say “this is what sucks about tracing, please fix it”, and then we can go fix it. It doesn’t really seem to happen that way tho, and for things like tracing ABI there just aren’t the right people in the room to have that kind of discussion. My proposal was just going to be a laundry list of things that would make my life easier, but it doesn’t really warrant a full micro-conference to listen to me bitch for an hour. If it turns out nobody else has much to talk about then we can just declare tracing is feature complete and we can talk about something else ;). Thanks,
Josef
next prev parent reply other threads:[~2017-06-30 18:38 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
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 [this message]
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=658A3F80-5E48-4EC4-A591-E3783AD3DADC@fb.com \
--to=jbacik@fb.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 \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.com \
/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