From: Jisheng Zhang <jszhang@marvell.com>
To: Doug Anderson <dianders@chromium.org>,
"wim@iguana.be" <wim@iguana.be>,
"linux@roeck-us.net" <linux@roeck-us.net>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] watchdog: dw_wdt: No need for a spinlock
Date: Fri, 8 May 2015 13:01:10 +0800 [thread overview]
Message-ID: <20150508130110.54cd965c@xhacker> (raw)
In-Reply-To: <1431059265-9204-1-git-send-email-dianders@chromium.org>
On Thu, 7 May 2015 21:27:44 -0700
Doug Anderson <dianders@chromium.org> wrote:
> Right now the dw_wdt uses a spinlock to protect dw_wdt_open(). The
> problem is that while holding the spinlock we call:
> -> dw_wdt_set_top()
> -> dw_wdt_top_in_seconds()
> -> clk_get_rate()
> -> clk_prepare_lock()
> -> mutex_lock()
>
> Locking a mutex while holding a spinlock is not allowed and leads to
> warnings like "BUG: spinlock wrong CPU on CPU#1", among other
> problems.
>
> There's no reason to use a spinlock. Only dw_wdt_open() was protected
> and the test_and_set_bit() at the start of that function protects us
> anyway.
>
> Signed-off-by: Doug Anderson <dianders@chromium.org>
> ---
> Changes in v2:
> - Don't switch to mutex; just don't use spinlock at all as per Dmitry
>
> drivers/watchdog/dw_wdt.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c
> index d0bb949..a284abd 100644
> --- a/drivers/watchdog/dw_wdt.c
> +++ b/drivers/watchdog/dw_wdt.c
> @@ -35,7 +35,6 @@
> #include <linux/pm.h>
> #include <linux/platform_device.h>
> #include <linux/reboot.h>
> -#include <linux/spinlock.h>
> #include <linux/timer.h>
> #include <linux/uaccess.h>
> #include <linux/watchdog.h>
> @@ -61,7 +60,6 @@ MODULE_PARM_DESC(nowayout, "Watchdog cannot be stopped once started "
> #define WDT_TIMEOUT (HZ / 2)
>
> static struct {
> - spinlock_t lock;
> void __iomem *regs;
> struct clk *clk;
> unsigned long in_use;
> @@ -177,7 +175,6 @@ static int dw_wdt_open(struct inode *inode, struct file *filp)
> /* Make sure we don't get unloaded. */
> __module_get(THIS_MODULE);
>
> - spin_lock(&dw_wdt.lock);
> if (!dw_wdt_is_enabled()) {
> /*
> * The watchdog is not currently enabled. Set the timeout to
> @@ -190,8 +187,6 @@ static int dw_wdt_open(struct inode *inode, struct file *filp)
>
> dw_wdt_set_next_heartbeat();
>
> - spin_unlock(&dw_wdt.lock);
> -
> return nonseekable_open(inode, filp);
> }
>
> @@ -348,8 +343,6 @@ static int dw_wdt_drv_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> - spin_lock_init(&dw_wdt.lock);
> -
> ret = misc_register(&dw_wdt_miscdev);
> if (ret)
> goto out_disable_clk;
Tested-by: Jisheng Zhang <jszhang@marvell.com>
next prev parent reply other threads:[~2015-05-08 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 4:27 [PATCH v2 1/2] watchdog: dw_wdt: No need for a spinlock Doug Anderson
2015-05-08 4:27 ` [PATCH v2 2/2] watchdog: dw_wdt: keepalive the watchdog at write time Doug Anderson
2015-05-08 5:24 ` Dmitry Torokhov
2015-05-08 4:51 ` [PATCH v2 1/2] watchdog: dw_wdt: No need for a spinlock Guenter Roeck
2015-05-08 5:01 ` Jisheng Zhang [this message]
2015-05-08 5:23 ` Dmitry Torokhov
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=20150508130110.54cd965c@xhacker \
--to=jszhang@marvell.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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.