From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: tglx@linutronix.de, peterz@infradead.org,
torvalds@linux-foundation.org, mingo@kernel.org,
rostedt@goodmis.org, linux-kernel@vger.kernel.org, man@keba.com,
hpa@zytor.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched, tracing: Fix trace_sched_pi_setprio() for deboosting
Date: Fri, 25 May 2018 11:54:07 +0200 [thread overview]
Message-ID: <20180525095407.g4qvfjzchbq7jusx@linutronix.de> (raw)
In-Reply-To: <tip-4ff648decf4712d39f184fc2df3163f43975575a@git.kernel.org>
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@linutronix.de>
> AuthorDate: Thu, 24 May 2018 15:26:48 +0200
> Committer: Ingo Molnar <mingo@kernel.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
prev parent reply other threads:[~2018-05-25 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 14:11 [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting Sebastian Andrzej Siewior
2018-05-23 17:28 ` Peter Zijlstra
2018-05-24 7:44 ` Sebastian Andrzej Siewior
2018-05-24 8:37 ` Peter Zijlstra
2018-05-24 8:41 ` Sebastian Andrzej Siewior
2018-05-24 13:26 ` [PATCH v2] " Sebastian Andrzej Siewior
2018-05-25 9:47 ` [tip:sched/core] sched, tracing: Fix " tip-bot for Sebastian Andrzej Siewior
2018-05-25 9:54 ` Sebastian Andrzej Siewior [this message]
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=20180525095407.g4qvfjzchbq7jusx@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=man@keba.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.