Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1437757
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH] tracing: add sched_prio_update |
| Date | 2016-07-06 16:20 +0200 |
| Message-ID | <rRVQd-1PF-19@gated-at.bofh.it> (permalink) |
| References | <rRica-1me-7@gated-at.bofh.it> <rRAiK-4z1-9@gated-at.bofh.it> <rRGxP-6u-13@gated-at.bofh.it> <rRUUa-1e4-11@gated-at.bofh.it> <rRVGx-1Ml-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, 6 Jul 2016 09:53:24 -0400 Julien Desfossez <jdesfossez@efficios.com> wrote: > > I'm not convinced this should be needed. I hate adding back to back > > tracepoints. > > Indeed, having two tracepoints back to back is not pretty. We placed it > here to get the priority of the newly created threads. Maybe a more > appropriate way of doing that would be to extend the sched_process_fork > tracepoint to output the same scheduling informations. Would you prefer > that option ? That may be a possibility. Let's see what Peter thinks. -- Steve
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[RFC PATCH] tracing: add sched_prio_update Julien Desfossez <jdesfossez@efficios.com> - 2016-07-04 22:00 +0200
Re: [RFC PATCH] tracing: add sched_prio_update Steven Rostedt <rostedt@goodmis.org> - 2016-07-05 17:20 +0200
Re: [RFC PATCH] tracing: add sched_prio_update Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-07-06 00:00 +0200
Re: [RFC PATCH] tracing: add sched_prio_update Steven Rostedt <rostedt@goodmis.org> - 2016-07-06 15:20 +0200
Re: [RFC PATCH] tracing: add sched_prio_update Julien Desfossez <jdesfossez@efficios.com> - 2016-07-06 16:10 +0200
Re: [RFC PATCH] tracing: add sched_prio_update Steven Rostedt <rostedt@goodmis.org> - 2016-07-06 16:20 +0200
csiph-web