From: Steven Rostedt <rostedt@goodmis.org>
To: Dima Zavin <dima@android.com>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] plist: add mutex to the blessed lock type for plists
Date: Wed, 29 Jun 2011 16:01:48 -0400 [thread overview]
Message-ID: <1309377708.26417.41.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1309376033-32005-1-git-send-email-dima@android.com>
On Wed, 2011-06-29 at 12:33 -0700, Dima Zavin wrote:
> +#include <linux/mutex.h>
> #include <linux/plist.h>
> #include <linux/spinlock.h>
>
> @@ -56,11 +57,14 @@ static void plist_check_list(struct list_head *top)
>
> static void plist_check_head(struct plist_head *head)
> {
> - WARN_ON(head != &test_head && !head->rawlock && !head->spinlock);
> + WARN_ON(head != &test_head && !head->rawlock && !head->spinlock &&
> + !head->mutex);
> if (head->rawlock)
> WARN_ON_SMP(!raw_spin_is_locked(head->rawlock));
> if (head->spinlock)
> WARN_ON_SMP(!spin_is_locked(head->spinlock));
> + if (head->mutex)
> + WARN_ON_SMP(!mutex_is_locked(head->mutex));
Spin locks are NOPs on SMP, but mutexes are not. Are you sure you want
this as WARN_ON_SMP()?
-- Steve
> if (!plist_head_empty(head))
> plist_check_list(&plist_first(head)->prio_list);
> plist_check_list(&head->node_list);
next prev parent reply other threads:[~2011-06-29 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 19:33 Dima Zavin
2011-06-29 20:01 ` Steven Rostedt [this message]
2011-06-29 20:10 ` Dima Zavin
2011-06-29 20:12 ` Dima Zavin
2011-06-29 20:13 ` Andi Kleen
2011-06-29 20:34 ` Dima Zavin
2011-06-29 20:43 ` Steven Rostedt
2011-06-30 22:14 ` Dima Zavin
2011-06-30 22:45 ` Steven Rostedt
2011-07-02 10:09 ` Peter Zijlstra
2011-06-29 20:36 ` Steven Rostedt
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=1309377708.26417.41.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=dima@android.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.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®