From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.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 17:03:05 -0700 [thread overview]
Message-ID: <CA+55aFxW_vhYWRoWFwy4zQgG7iPJg3V4u0-XkjZiGJJfZtZ=ng@mail.gmail.com> (raw)
In-Reply-To: <20170629195537.534445e7@gandalf.local.home>
On Thu, Jun 29, 2017 at 4:55 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>>
>> * 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.
>
> One way is to fix all tools that use it and make sure they get out to
> the distros before making the change.
OR DO THE THING THAT PEOPLE HAVE BEEN TOLD TO DO AT LEAST THREE KERNEL
SUMMITS NOW: LEAVE THE DAMN FIELD ALONE, AND FILL IT WITH ZERO. OR
ONE. OR BRAN MUFFINS. I DON'T CARE. BUT DON'T REMOVE IT, AND STOP
USING IT AS AN EXCUSE FOR WHY NOTHING CAN EVER BE DONE.
Really. I don't want to have this stupid tracing discussion one more
time. We've had it. Several times. This exact issue has come up.
Several times.
So stop wasting everybodys time one more year. I'm going to walk out
if people start discussing this thing again.
Linus "grumpy"
next prev parent reply other threads:[~2017-06-30 0:03 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 [this message]
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='CA+55aFxW_vhYWRoWFwy4zQgG7iPJg3V4u0-XkjZiGJJfZtZ=ng@mail.gmail.com' \
--to=torvalds@linux-foundation.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=rostedt@goodmis.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