[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180525095407.g4qvfjzchbq7jusx@linutronix.de>
Date: Fri, 25 May 2018 11:54:07 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: tglx@...utronix.de, peterz@...radead.org,
torvalds@...ux-foundation.org, mingo@...nel.org,
rostedt@...dmis.org, linux-kernel@...r.kernel.org, man@...a.com,
hpa@...or.com
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched, tracing: Fix trace_sched_pi_setprio()
for deboosting
On 2018-05-25 02:47:20 [-0700], tip-bot for Sebastian Andrzej Siewior wrote:
> Commit-ID: 4ff648decf4712d39f184fc2df3163f43975575a
> Gitweb: https://git.kernel.org/tip/4ff648decf4712d39f184fc2df3163f43975575a
> Author: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> AuthorDate: Thu, 24 May 2018 15:26:48 +0200
> Committer: Ingo Molnar <mingo@...nel.org>
> CommitDate: Fri, 25 May 2018 08:04:01 +0200
>
> sched, tracing: Fix trace_sched_pi_setprio() for deboosting
>
> Since the following commit:
>
> b91473ff6e97 ("sched,tracing: Update trace_sched_pi_setprio()")
>
> the sched_pi_setprio trace point shows the "newprio" during a deboost:
>
> |futex sched_pi_setprio: comm=futex_requeue_p pid"34 oldprio newprio=3D98
> |futex sched_switch: prev_comm=futex_requeue_p prev_pid"34 prev_prio=120
pid=2234 got turned into pid"34 the same for other fields.
Sebastian
Powered by blists - more mailing lists