public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 07 May 2014 11:07:17 +0200	[thread overview]
Message-ID: <1399453637.5142.40.camel@marge.simpson.net> (raw)
In-Reply-To: <5369EC9E.1010904@linutronix.de>

On Wed, 2014-05-07 at 10:19 +0200, Sebastian Andrzej Siewior wrote: 
> On 05/03/2014 07:03 PM, Mike Galbraith wrote:
> >> Mike, I see that lockdep splat (sleeping while atomic) during cpu-hotplug.
> >> Don't you see this, too?
> > 
> > Nope, didn't.
> 
> Hmm. blk_mq_hctx_notify(). It does
> 	spin_lock(&ctx->lock);
> 
> Isn't this a sleeping spinlock for you or don't get here at all?

Hm, cts->lock...

git@marge:~/suse/scratch_area/linux-3.12-SLE12-RT> grep -IR cpu_lock block
git@marge:~/suse/scratch_area/linux-3.12-SLE12-RT>

(here lock lock lock, here boy)

marge:/usr/local/src/kernel/linux-3.x.git # grep -IR cpu_lock block
marge:/usr/local/src/kernel/linux-3.x.git # 

marge:/usr/local/src/kernel/linux-3.14 # grep -IR cpu_lock block
marge:/usr/local/src/kernel/linux-3.14 #

(what the..)

marge:/usr/local/src/kernel/linux-3.14-rt # grep -IR cpu_lock block
block/blk-mq.c: spin_lock(&ctx->cpu_lock);
block/blk-mq.c: spin_unlock(&ctx->cpu_lock);
block/blk-mq.c:                         spin_unlock(&ctx->cpu_lock);
block/blk-mq.c:                         spin_lock(&ctx->cpu_lock);
block/blk-mq.c:         spin_lock_init(&__ctx->cpu_lock);
block/blk-mq.h: spinlock_t              cpu_lock;
marge:/usr/local/src/kernel/linux-3.14-rt #

(aha!)

Nope, I definitely don't get there.

	-Mike


      reply	other threads:[~2014-05-07  9:07 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
2014-05-07  8:19   ` Sebastian Andrzej Siewior
2014-05-07  9:07     ` Mike Galbraith [this message]

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=1399453637.5142.40.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