From: Alex Shi <alex.shi@linaro.org>
To: mathieu.poirier@linaro.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org (open list:LOCKING PRIMITIVES)
Cc: Alex Shi <alex.shi@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v2 3/3] rtmutex: remove unnecessary adjust prio
Date: Fri, 21 Apr 2017 22:12:55 +0800 [thread overview]
Message-ID: <1492783975-13633-3-git-send-email-alex.shi@linaro.org> (raw)
In-Reply-To: <1492783975-13633-1-git-send-email-alex.shi@linaro.org>
We don't need to adjust prio before new pi_waiter adding. The prio
only need update after pi_waiter change or task priority change.
Signed-off-by: Alex Shi <alex.shi@linaro.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org
To: Ingo Molnar <mingo@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
---
kernel/locking/rtmutex.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index b955094..b659ba0 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -963,7 +963,6 @@ static int task_blocks_on_rt_mutex(struct rt_mutex *lock,
return -EDEADLK;
raw_spin_lock(&task->pi_lock);
- rt_mutex_adjust_prio(task);
waiter->task = task;
waiter->lock = lock;
waiter->prio = task->prio;
--
1.9.1
next prev parent reply other threads:[~2017-04-21 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 14:12 [PATCH v2 1/3] rtmutex: update rt-mutex-design Alex Shi
2017-04-21 14:12 ` [PATCH v2 2/3] rtmutex: update rt-mutex Alex Shi
2017-04-21 14:12 ` Alex Shi [this message]
2017-04-21 15:47 ` [PATCH v2 1/3] rtmutex: update rt-mutex-design Peter Zijlstra
2017-04-24 13:39 ` Alex Shi
2017-04-21 15:57 ` Mathieu Poirier
2017-04-24 13:45 ` Alex Shi
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=1492783975-13633-3-git-send-email-alex.shi@linaro.org \
--to=alex.shi@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).