Subject: Re: Ingo's  realtime_preempt patch causes kernel oops
From: Sven-Thorsten Dietrich <sven@mvista.com>
To: tglx@linutronix.de
Cc: Steven Rostedt <rostedt@goodmis.org>, Yann.LEPROVOST@wavecom.fr,
       Daniel Walker <dwalker@mvista.com>, linux-kernel@vger.kernel.org,
       linux-kernel-owner@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
In-Reply-To: <1148476383.5239.54.camel@localhost.localdomain>
References: <OFD8B7556E.13DD6F3A-ONC1257178.002C2D9A-C1257178.002D1FC5@wavecom.fr>
	 <1148475334.24623.45.camel@localhost.localdomain>
	 <1148476383.5239.54.camel@localhost.localdomain>
Content-Type: text/plain
Organization: MontaVista Software, Inc.
Date: Wed, 24 May 2006 08:32:08 -0700
Message-Id: <1148484729.14683.5.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 893
Lines: 24

On Wed, 2006-05-24 at 15:13 +0200, Thomas Gleixner wrote:
> On Wed, 2006-05-24 at 08:55 -0400, Steven Rostedt wrote:
> > Thomas or Ingo,
> > 
> > Maybe the handling of IRQs needs to handle the case that shared irq can
> > have both a NODELAY and a thread.  The irq descriptor could have a
> > NODELAY set if any of the actions are NODELAY, but before calling the
> > interrupt handler (in interrupt context), check if the action is NODELAY
> > or not, and if not, wake up the thread if not done so already.
> 
> As I said yesterday. You need a demultiplexer for such cases.
> 

Would IRQs stay masked until the thread has finished running?

Sven


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/