From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: Thomas Meyer <thomas@m3y3r.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"Berg, Johannes" <johannes.berg@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Intel Linux Wireless <ilw@linux.intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [Ilw] Re: Kernel panic in 3.10.10-rt7 (iwlwifi)
Date: Mon, 07 Oct 2013 09:33:11 +0200 [thread overview]
Message-ID: <525263B7.5090609@linutronix.de> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB301DBC098@HASMSX103.ger.corp.intel.com>
On 10/06/2013 08:00 AM, Grumbach, Emmanuel wrote:
>
> We have a patch internally that goes into that direction, but one thing though.
Sounds great.
> If you still have a spinlock in the primary handler, wouldn't that sleep in a non-sleepable context? Forgive my -rt ignorance, but I understood that in -rt, all the spinlock go to sleep which basically mean that we can't take any spinlock in the primary irq handler so I am a bit confused here.
After my change there is no primary handler anymore, just the threaded
where you can take the (sleeping) spinlock.
Everything what you wrote is correct:
- you can't take a spinlock in the primary handler
- all spinlocks may sleep
Sebastian
prev parent reply other threads:[~2013-10-07 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2CD18B42-2489-4DF7-98D6-4D002329DC63@m3y3r.de>
2013-10-04 10:12 ` Kernel panic in 3.10.10-rt7 (iwlwifi) Sebastian Andrzej Siewior
2013-10-06 6:00 ` [Ilw] " Grumbach, Emmanuel
2013-10-07 7:33 ` Sebastian Andrzej Siewior [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=525263B7.5090609@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.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;
as well as URLs for NNTP newsgroup(s).