[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0805021441340.10615@gandalf.stny.rr.com>
Date: Fri, 2 May 2008 14:45:25 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Sven-Thorsten Dietrich <sven@...bigcorporation.com>
cc: Remy Bohmer <linux@...mer.net>,
LKML <linux-kernel@...r.kernel.org>,
RT <linux-rt-users@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jon Masters <jonathan@...masters.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Preempt-RT patch for 2.6.25
On Fri, 2 May 2008, Sven-Thorsten Dietrich wrote:
>
>
> His bi-sectability changes are pretty key, and I would like to see those
> reviewed and incorporated, even if they apply only to x86.
They would be nice, but I'm also in the process of moving patches around
to have the next mainline enhancement up front.
>
> The RT patch queue generally is a mess today.
> Lots of stuff needs to be folded down into the core patches.
I'm starting to fold patches together too.
>
> The ins and outs of the softirq code need major clean-up.
That's my next project after ftrace.
>
> There are big issues around apic / hardirq threads that we need to
> tackle at multiple levels.
This is also being worked on by tglx and Jon Masters.
>
> (we are seeing the semis acknowledge the IRQ thread model, where IRQs
> may stay masked longer than usual)
>
> per-device irq threads, as Jon Masters has mentioned in his blog, may be
> one work-around to get past the legacy stuff in x86.
>
> and with the x86 merge, all this should become easier, so that hopefully
> we can extricate the IRQ threads changes in a bisectable way, so we can
> address the technical issues that stand in the way of upstream, apart
> from PREEMPT_RT.
Yeah, I'll be starting to take a hard crack at getting the irqs as threads
work ready for mainline soon.
As for 2.6.25-rt1, I'm currently working on it. I have the patch queue
ready, but it has some major bugs that I'm stil working out. I did a bit
of clean up in the per-cpu portion as well as some of the mutex code. Now
I need to debug all those changes.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists