From: Steven Rostedt <rostedt@goodmis.org>
To: Yann.LEPROVOST@wavecom.fr
Cc: Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Ingo's realtime_preempt patch causes kernel oops
Date: Tue, 23 May 2006 13:00:42 -0400 [thread overview]
Message-ID: <1148403642.22855.12.camel@localhost.localdomain> (raw)
In-Reply-To: <OF75506F98.64DD61BC-ONC1257177.005A42A4-C1257177.005AF51F@wavecom.fr>
On Tue, 2006-05-23 at 18:27 +0200, Yann.LEPROVOST@wavecom.fr wrote:
> I forgot to say that I let SA_SHIRQ as the IRQ line is shared...
> It seems to work correctly...
What shares it?
Reason I ask, is that this irq is now running in true interrupt context,
and that on PREEMPT_RT the spin_locks are mutexes and can schedule. So
if another device is sharing this irq, then its interrupt handler will
be running in interrupt context, and if it grabs a spin_lock than is not
a raw_spinlock_t then you will have a crash.
This won't be a problem if you only turn on Hard irqs as threads and
don't do the PREEMPT_RT.
-- Steve
next prev parent reply other threads:[~2006-05-23 17:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 13:40 Ingo's realtime_preempt patch causes kernel oops Yann.LEPROVOST
2006-05-23 14:09 ` Steven Rostedt
2006-05-23 14:19 ` Steven Rostedt
2006-05-23 14:26 ` Thomas Gleixner
2006-05-23 15:33 ` Daniel Walker
2006-05-23 16:02 ` Steven Rostedt
2006-05-23 16:27 ` Yann.LEPROVOST
2006-05-23 17:00 ` Steven Rostedt [this message]
2006-05-23 17:10 ` Yann.LEPROVOST
2006-05-23 18:21 ` Steven Rostedt
2006-05-24 8:06 ` Yann.LEPROVOST
2006-05-24 12:55 ` Steven Rostedt
2006-05-24 13:13 ` Thomas Gleixner
2006-05-24 15:32 ` Sven-Thorsten Dietrich
2006-05-24 15:52 ` Steven Rostedt
2006-05-24 16:03 ` Thomas Gleixner
2006-05-24 16:38 ` Steven Rostedt
2006-05-24 16:55 ` Thomas Gleixner
2006-05-24 17:09 ` Sven-Thorsten Dietrich
2006-05-24 16:06 ` Daniel Walker
2006-05-24 13:58 ` Yann.LEPROVOST
2006-05-24 16:43 ` Esben Nielsen
2006-05-24 17:06 ` Thomas Gleixner
2006-05-24 18:00 ` Sven-Thorsten Dietrich
2006-05-30 10:00 ` RT_PREEMPT problem with cascaded irqchip Yann.LEPROVOST
2006-05-30 10:27 ` Thomas Gleixner
2006-05-30 10:26 ` Yann.LEPROVOST
2006-05-30 11:22 ` Thomas Gleixner
2006-05-30 14:44 ` Yann.LEPROVOST
2006-05-30 23:25 ` Thomas Gleixner
2006-05-31 8:26 ` Yann.LEPROVOST
2006-05-24 17:30 ` Ingo's realtime_preempt patch causes kernel oops Sven-Thorsten Dietrich
[not found] <OF928FB2B7.5CE25C69-ONC1257177.00596B7A-C1257177.005AAA6F@wavecom.fr>
2006-05-23 16:38 ` Daniel Walker
2006-05-23 16:44 ` Thomas Gleixner
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=1148403642.22855.12.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=Yann.LEPROVOST@wavecom.fr \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.