public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Yann.LEPROVOST@wavecom.fr, sdietrich@mvista.com,
	Takeharu KATO <takeharu1219@ybb.ne.jp>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Ingo's  realtime_preempt patch causes kernel oops
Date: Tue, 23 May 2006 18:44:48 +0200	[thread overview]
Message-ID: <1148402688.5239.37.camel@localhost.localdomain> (raw)
In-Reply-To: <1148402326.3535.95.camel@c-67-180-134-207.hsd1.ca.comcast.net>

On Tue, 2006-05-23 at 09:38 -0700, Daniel Walker wrote:
> On Tue, 2006-05-23 at 18:24 +0200, Yann.LEPROVOST@wavecom.fr wrote:
> > Yeah that's it , I tested with SA_NODELAY and oops disappears, kernel
> > doesn't freeze !!
> > 
> > However, the IRQ 1 line is shared between many peripherals in the
> > AT91RM9200...
> > IRQ 1 is the system interrupt.
> > 
> > From AT91RM9200 datasheet :
> > 
> > "The System Interrupt is the wired-OR of the interrupt signals coming from:
> > • the Memory Controller
> > • the Debug Unit
> > • the System Timer
> > • the Real-Time Clock
> > • the Power Management Controller"
> > 
> 
> You might have some more issues , cause if you share an SA_NODELAY
> handler every handler on that interrupt line becomes an SA_NODELAY
> handler .. So you'll have to go make sure non of those other handlers
> lock spinlock_t types ..

The best solution is probably a demultiplex handler.

	tglx



  reply	other threads:[~2006-05-24  7:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF928FB2B7.5CE25C69-ONC1257177.00596B7A-C1257177.005AAA6F@wavecom.fr>
2006-05-23 16:38 ` Ingo's realtime_preempt patch causes kernel oops Daniel Walker
2006-05-23 16:44   ` Thomas Gleixner [this message]
2006-05-23 13:40 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
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-24 17:30                     ` Sven-Thorsten Dietrich

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=1148402688.5239.37.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=Yann.LEPROVOST@wavecom.fr \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sdietrich@mvista.com \
    --cc=takeharu1219@ybb.ne.jp \
    /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