Re: [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

On 2018-05-24 10:37:54 [+0200], Peter Zijlstra wrote: > Thing is, with the pi_task as an argument, someone using the tracehook > can actually get the deadline data out, even if the normal 'event' does > not. Okay, in that case an update will follow shortly. Sebastian

Re: [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

On Thu, May 24, 2018 at 09:44:14AM +0200, Sebastian Andrzej Siewior wrote: > On 2018-05-23 19:28:19 [+0200], Peter Zijlstra wrote: > > On Wed, May 23, 2018 at 04:11:07PM +0200, Sebastian Andrzej Siewior wrote: > > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > > index 092f7c4de903..8

Re: [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

On 2018-05-23 19:28:19 [+0200], Peter Zijlstra wrote: > On Wed, May 23, 2018 at 04:11:07PM +0200, Sebastian Andrzej Siewior wrote: > > > Since that commit I see during a deboost a task this: > > |futex sched_pi_setprio: comm=futex_requeue_p pid=2234 oldprio=98 newprio=98 > > |futex sched_switch: p

Re: [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

On Wed, May 23, 2018 at 04:11:07PM +0200, Sebastian Andrzej Siewior wrote: > Since that commit I see during a deboost a task this: > |futex sched_pi_setprio: comm=futex_requeue_p pid=2234 oldprio=98 newprio=98 > |futex sched_switch: prev_comm=futex_requeue_p prev_pid=2234 prev_prio=120 > > and af

[PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

This mostly a revert of commit b91473ff6e97 ("sched,tracing: Update trace_sched_pi_setprio()") except for the XXX comments. Since that commit I see during a deboost a task this: |futex sched_pi_setprio: comm=futex_requeue_p pid=2234 oldprio=98 newprio=98 |futex sched_switch: prev_comm=futex_requeue