From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH RT] blk-mq: revert raw locks, post pone notifier to POST_DEAD
Date: Sat, 03 May 2014 19:03:07 +0200 [thread overview]
Message-ID: <1399136587.5158.29.camel@marge.simpson.net> (raw)
In-Reply-To: <1399135344-5349-1-git-send-email-bigeasy@linutronix.de>
On Sat, 2014-05-03 at 18:42 +0200, Sebastian Andrzej Siewior wrote:
> The blk_mq_cpu_notify_lock should be raw because some CPU down levels
> are called with interrupts off. The notifier itself calls currently one
> function that is blk_mq_hctx_notify().
> That function acquires the ctx->lock lock which is sleeping and I would
> prefer to keep it that way. That function only moves IO-requests from
> the CPU that is going offline to another CPU and it is currently the
> only one. Therefore I revert the list lock back to sleeping spinlocks
> and let the notifier run at POST_DEAD time.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> Mike, I see that lockdep splat (sleeping while atomic) during cpu-hotplug.
> Don't you see this, too?
Nope, didn't.
> block/blk-mq-cpu.c | 17 ++++++++++-------
> block/blk-mq.c | 2 +-
> 2 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/block/blk-mq-cpu.c b/block/blk-mq-cpu.c
> index 136ef86..37acc3a 100644
> --- a/block/blk-mq-cpu.c
> +++ b/block/blk-mq-cpu.c
> @@ -11,7 +11,7 @@
> #include "blk-mq.h"
>
> static LIST_HEAD(blk_mq_cpu_notify_list);
> -static DEFINE_RAW_SPINLOCK(blk_mq_cpu_notify_lock);
> +static DEFINE_SPINLOCK(blk_mq_cpu_notify_lock);
>
> static int blk_mq_main_cpu_notify(struct notifier_block *self,
> unsigned long action, void *hcpu)
> @@ -19,12 +19,15 @@ static int blk_mq_main_cpu_notify(struct notifier_block *self,
> unsigned int cpu = (unsigned long) hcpu;
> struct blk_mq_cpu_notifier *notify;
>
> - raw_spin_lock(&blk_mq_cpu_notify_lock);
> + if (action != CPU_POST_DEAD && action != CPU_POST_DEAD)
> + return NOTIFY_OK;
> +
> + spin_lock(&blk_mq_cpu_notify_lock);
>
> list_for_each_entry(notify, &blk_mq_cpu_notify_list, list)
> notify->notify(notify->data, action, cpu);
>
> - raw_spin_unlock(&blk_mq_cpu_notify_lock);
> + spin_unlock(&blk_mq_cpu_notify_lock);
> return NOTIFY_OK;
> }
>
> @@ -32,16 +35,16 @@ void blk_mq_register_cpu_notifier(struct blk_mq_cpu_notifier *notifier)
> {
> BUG_ON(!notifier->notify);
>
> - raw_spin_lock(&blk_mq_cpu_notify_lock);
> + spin_lock(&blk_mq_cpu_notify_lock);
> list_add_tail(¬ifier->list, &blk_mq_cpu_notify_list);
> - raw_spin_unlock(&blk_mq_cpu_notify_lock);
> + spin_unlock(&blk_mq_cpu_notify_lock);
> }
>
> void blk_mq_unregister_cpu_notifier(struct blk_mq_cpu_notifier *notifier)
> {
> - raw_spin_lock(&blk_mq_cpu_notify_lock);
> + spin_lock(&blk_mq_cpu_notify_lock);
> list_del(¬ifier->list);
> - raw_spin_unlock(&blk_mq_cpu_notify_lock);
> + spin_unlock(&blk_mq_cpu_notify_lock);
> }
>
> void blk_mq_init_cpu_notifier(struct blk_mq_cpu_notifier *notifier,
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index da3af9f..d5e73d8 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -971,7 +971,7 @@ static void blk_mq_hctx_notify(void *data, unsigned long action,
> struct blk_mq_ctx *ctx;
> LIST_HEAD(tmp);
>
> - if (action != CPU_DEAD && action != CPU_DEAD_FROZEN)
> + if (action != CPU_POST_DEAD && action != CPU_POST_DEAD)
> return;
>
> /*
next prev parent reply other threads:[~2014-05-03 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 16:42 [PATCH RT] blk-mq: revert raw locks, post pone notifier to POST_DEAD Sebastian Andrzej Siewior
2014-05-03 17:03 ` Mike Galbraith [this message]
2014-05-07 8:19 ` Sebastian Andrzej Siewior
2014-05-07 9:07 ` Mike Galbraith
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=1399136587.5158.29.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
/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