Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1533571

[patch 3/4] rtmutex: Get rid of RT_MUTEX_OWNER_MASKALL

From Thomas Gleixner <tglx@linutronix.de>
Newsgroups linux.kernel
Subject [patch 3/4] rtmutex: Get rid of RT_MUTEX_OWNER_MASKALL
Date 2016-11-30 22:10 +0100
Message-ID <sJkiB-2NQ-19@gated-at.bofh.it> (permalink)
References <sJkiB-2NQ-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


This is a left over from the original rtmutex implementation which used
both bit0 and bit1 in the owner pointer. Commit 8161239a8bcc ("rtmutex:
Simplify PI algorithm and make highest prio task get lock") removed the
usage of bit1, but kept the extra mask around. This is confusing at best.

Remove it and just use RT_MUTEX_HAS_WAITERS for the masking.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 kernel/locking/rtmutex_common.h |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

--- a/kernel/locking/rtmutex_common.h
+++ b/kernel/locking/rtmutex_common.h
@@ -71,13 +71,12 @@ task_top_pi_waiter(struct task_struct *p
  * lock->owner state tracking:
  */
 #define RT_MUTEX_HAS_WAITERS	1UL
-#define RT_MUTEX_OWNER_MASKALL	1UL
 
 static inline struct task_struct *rt_mutex_owner(struct rt_mutex *lock)
 {
 	unsigned long owner = (unsigned long) READ_ONCE(lock->owner);
 
-	return (struct task_struct *) (owner & ~RT_MUTEX_OWNER_MASKALL);
+	return (struct task_struct *) (owner & ~RT_MUTEX_HAS_WAITERS);
 }
 
 /*

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[patch 3/4] rtmutex: Get rid of RT_MUTEX_OWNER_MASKALL Thomas Gleixner <tglx@linutronix.de> - 2016-11-30 22:10 +0100
  [tip:locking/core] locking/rtmutex: Get rid of  RT_MUTEX_OWNER_MASKALL tip-bot for Thomas Gleixner <tipbot@zytor.com> - 2016-12-02 11:50 +0100

csiph-web