[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0909230922160.2981@nanos>
Date: Wed, 23 Sep 2009 09:25:06 -0700 (PDT)
From: Thomas Gleixner <tglx@...utronix.de>
To: Jan Blunck <jblunck@...e.de>
cc: LKML <linux-kernel@...r.kernel.org>,
rt-users <linux-rt-users@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Carsten Emde <ce@...g.ch>,
Clark Williams <williams@...hat.com>,
Frank Rowand <frank.rowand@...sony.com>,
Robin Gareus <robin@...eus.org>,
Gregory Haskins <ghaskins@...ell.com>,
Philippe Reynes <philippe.reynes@...smpp.fr>,
Fernando Lopez-Lezcano <nando@...ma.stanford.edu>,
Will Schmidt <will_schmidt@...t.ibm.com>,
Darren Hart <dvhltc@...ibm.com>,
Sven-Thorsten Dietrich <sdietrich@...ell.com>,
Jon Masters <jcm@...hat.com>,
Mark Knecht <markknecht@...il.com>
Subject: Re: [ANNOUNCE] 2.6.31-rt11
On Wed, 23 Sep 2009, Jan Blunck wrote:
> On Sat, Sep 19, 2009 at 12:39 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> > We are pleased to announce the next update to our new preempt-rt
> > series.
> >
> > - disable SPARSE_IRQ, DMAR, IRQ_REMAP for -rt
> >
>
> Do you have any reports that there is a bug in the SPARSE_IRQ code or
> why did you disable it?
Sparse irq is allocating memory in irq/preempt disabled regions which
makes preempt debug pretty unhappy. It needs some restructuring of
that code. dmar and irqremap have the same problem.
Thanks,
tglx
Powered by blists - more mailing lists