From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH V2 3/3] sched/deadline: Tracepoints for deadline scheduler
Date: Tue, 29 Mar 2016 23:03:43 +0200 [thread overview]
Message-ID: <20160329210343.GP3408@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <56FAEC3D.1070300@redhat.com>
> And any change on it, now and in the future, will cause confusion for
> 99.999% of raw sched_switch users.
Sod that, this attitude makes me want to rip out all sched tracepoints.
> Without considering those who wrote bad applications that will break,
That's bonus points, right?
I'm seriously annoyed with this hard ABI for tracepoints crap.
next prev parent reply other threads:[~2016-03-29 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 16:50 [PATCH V2 0/3] Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-03-28 16:50 ` [PATCH V2 1/3] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers Daniel Bristot de Oliveira
2016-03-28 16:50 ` [PATCH V2 2/3] sched: Move deadline container_of() helper functions into sched.h Daniel Bristot de Oliveira
2016-03-28 16:50 ` [PATCH V2 3/3] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira
2016-03-29 15:16 ` Peter Zijlstra
2016-03-29 15:57 ` Steven Rostedt
2016-03-29 16:04 ` Peter Zijlstra
2016-03-29 17:10 ` Steven Rostedt
2016-03-29 20:11 ` Peter Zijlstra
2016-03-29 20:29 ` Steven Rostedt
2016-03-29 20:46 ` Peter Zijlstra
2016-03-29 20:57 ` Daniel Bristot de Oliveira
2016-03-29 21:03 ` Peter Zijlstra [this message]
2016-03-29 21:49 ` Steven Rostedt
2016-03-29 17:37 ` Daniel Bristot de Oliveira
2016-03-29 18:10 ` Steven Rostedt
2016-03-29 16:10 ` Daniel Bristot de Oliveira
2016-03-29 17:13 ` Steven Rostedt
2016-03-29 19:12 ` Daniel Bristot de Oliveira
2016-03-29 19:25 ` Steven Rostedt
2016-03-31 5:19 ` Juri Lelli
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=20160329210343.GP3408@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=bristot@redhat.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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