From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Brad Mouring <bmouring@ni.com>
Subject: Re: [patch 2/2] rtmutex: Detect changes in the pi lock chain
Date: Fri, 6 Jun 2014 05:58:29 -0400 [thread overview]
Message-ID: <20140606055829.3f214902@gandalf.local.home> (raw)
In-Reply-To: <20140606094859.GW6758@twins.programming.kicks-ass.net>
On Fri, 6 Jun 2014 11:48:59 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
>
>
> hehe, I can almost follow this code :-)
>
> How about something like this on top?
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
>
> ---
> --- a/kernel/locking/rtmutex.c
> +++ b/kernel/locking/rtmutex.c
> @@ -260,6 +260,11 @@ static void rt_mutex_adjust_prio(struct
> */
> int max_lock_depth = 1024;
>
> +static inline struct rt_mutex *task_blocked_on(struct task_struct *p)
> +{
> + return p->pi_blocked_on ? p->pi_blocked_on->lock : NULL;
> +}
> +
> /*
> * Adjust the priority chain. Also used for deadlock detection.
> * Decreases task's usage by one - may thus free the task.
> @@ -443,10 +448,7 @@ static int rt_mutex_adjust_prio_chain(st
> * blocked itself. If yes we store a pointer to the lock for
> * the lock chain change detection above.
> */
> - if (task->pi_blocked_on)
> - next_lock = task->pi_blocked_on->lock;
> - else
> - next_lock = NULL;
> + next_lock = task_blocked_on(task);
>
> raw_spin_unlock_irqrestore(&task->pi_lock, flags);
>
> @@ -569,7 +571,7 @@ static int task_blocks_on_rt_mutex(struc
> {
> struct task_struct *owner = rt_mutex_owner(lock);
> struct rt_mutex_waiter *top_waiter = waiter;
> - struct rt_mutex *next_lock = NULL;
> + struct rt_mutex *next_lock;
> unsigned long flags;
> int chain_walk, res;
>
> @@ -614,8 +616,8 @@ static int task_blocks_on_rt_mutex(struc
> } else if (debug_rt_mutex_detect_deadlock(waiter, detect_deadlock)) {
> chain_walk = 1;
> }
> - if (owner->pi_blocked_on)
> - next_lock = owner->pi_blocked_on->lock;
> +
> + next_lock = task_blocked_on(owner);
>
> raw_spin_unlock_irqrestore(&owner->pi_lock, flags);
> if (!chain_walk)
> @@ -705,8 +707,7 @@ static void remove_waiter(struct rt_mute
> }
> __rt_mutex_adjust_prio(owner);
>
> - if (owner->pi_blocked_on)
> - next_lock = owner->pi_blocked_on->lock;
> + next_lock = task_blocked_on(owner);
>
> raw_spin_unlock_irqrestore(&owner->pi_lock, flags);
> }
next prev parent reply other threads:[~2014-06-06 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 15:28 [patch 0/2] rtmutex: Sanitze deadlock detection and chain walk Thomas Gleixner
2014-06-05 15:28 ` [patch 1/2] rtmutex: Handle deadlock detection smarter Thomas Gleixner
2014-06-06 1:14 ` Steven Rostedt
2014-06-06 5:41 ` Thomas Gleixner
2014-06-06 2:59 ` Steven Rostedt
2014-06-06 5:40 ` Thomas Gleixner
2014-06-09 16:49 ` [tip:locking/urgent] " tip-bot for Thomas Gleixner
2014-06-05 15:28 ` [patch 2/2] rtmutex: Detect changes in the pi lock chain Thomas Gleixner
2014-06-06 9:48 ` Peter Zijlstra
2014-06-06 9:58 ` Steven Rostedt [this message]
2014-06-06 14:25 ` Steven Rostedt
2014-06-06 14:49 ` Steven Rostedt
2014-06-07 7:31 ` Thomas Gleixner
2014-06-09 16:49 ` [tip:locking/urgent] " tip-bot for Thomas Gleixner
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=20140606055829.3f214902@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bmouring@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®