ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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 18:00:42 -0700	[thread overview]
Message-ID: <CA+55aFyQE_T7Rp7ay_EbAZNDqLE6ffJ-6xkL6B_961oZ0+aSpA@mail.gmail.com> (raw)
In-Reply-To: <20170629205218.5b9a7923@gandalf.local.home>

On Thu, Jun 29, 2017 at 5:52 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Just to explain what Mathieu was talking about with echo and such, is
> that Peter Zijlstra has been against multiple tracepoints for that one
> sched switch location.

I am too.

Dammit, if somebody cares about one partiocular scheduler, then that
person can add dynamic tracepoints.

Leave the existing one alone. Really. Zero out any fields that no
longer make sense. Really. Don't beat this damn horse again. It's been
dead for three years, and it's not just smelling bad, it's bloating in
some scary ways.

The only reason for static tracepoints are for major tools like
powertop. There is no way in hell such a tool will care about fields
that only exist for one particular scheduler implementation. Don't add
new random crap.

If somebody is interested in *one* particular odd low-level scheduler,
he damn well can add the dynamic points.

This is the last I want to ever hear about it, and I particularly do
not want to have this be a kernel summit discussion. We've had it
before. Get over it.

                Linus

  reply	other threads:[~2017-06-30  1:00 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 [this message]
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+55aFyQE_T7Rp7ay_EbAZNDqLE6ffJ-6xkL6B_961oZ0+aSpA@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