Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1339754
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler |
| Date | 2016-02-22 18:50 +0100 |
| Message-ID | <r52Mq-VA-3@gated-at.bofh.it> (permalink) |
| References | <r529I-AD-9@gated-at.bofh.it> <r529I-AD-17@gated-at.bofh.it> <r52CJ-Rl-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 22 Feb 2016 18:32:59 +0100 Peter Zijlstra <peterz@infradead.org> wrote: > So I'm a bit allergic to tracepoints and this is very flimsy on reasons > why I would want to do this. Because there's no way to know if SCHED_DEADLINE tasks are doing what they suppose to without hacking the kernel and adding your own tracepoints. > > As it stands, the existing tracepoint have already been an ABI > trainwreck, why would I want to add more? Yes, this may become a type of ABI, but even the sched switch tracepoints haven't been that bad. Has it really prevented us from changing anything? "trainwreck" is a harsh word, and the information of scheduling tracepoints have been crucial to finding bugs and such. And has been tremendously useful in loads of cases. But let me ask, what would you recommend to finding out if the kernel has really given your tasks the recommended runtime within a given period? We can't expect users of SCHED_DEADLINE to be modifying the kernel themselves. -- Steve
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira <bristot@redhat.com> - 2016-02-22 18:10 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Peter Zijlstra <peterz@infradead.org> - 2016-02-22 18:40 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Steven Rostedt <rostedt@goodmis.org> - 2016-02-22 18:50 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira <bristot@redhat.com> - 2016-02-22 21:20 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Peter Zijlstra <peterz@infradead.org> - 2016-02-22 22:40 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Steven Rostedt <rostedt@goodmis.org> - 2016-02-22 23:40 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Juri Lelli <juri.lelli@arm.com> - 2016-02-23 11:40 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Peter Zijlstra <peterz@infradead.org> - 2016-02-23 11:50 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Steven Rostedt <rostedt@goodmis.org> - 2016-02-23 14:20 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Ingo Molnar <mingo@kernel.org> - 2016-02-24 09:50 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Peter Zijlstra <peterz@infradead.org> - 2016-02-23 15:30 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira <bristot@redhat.com> - 2016-02-23 17:20 +0100
Re: [PATCH 3/4] sched/deadline: Tracepoints for deadline scheduler Daniel Bristot de Oliveira <bristot@redhat.com> - 2016-02-24 03:30 +0100
csiph-web