mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
To: Remy Bohmer <linux@bohmer.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>
Subject: Re: Preempt-RT patch for 2.6.25
Date: Fri, 02 May 2008 11:34:10 -0700	[thread overview]
Message-ID: <1209753250.25628.34.camel@dd.thebigcorporation.com> (raw)
In-Reply-To: <3efb10970805021102n4d87f55eue723786281b06fcb@mail.gmail.com>


On Fri, 2008-05-02 at 20:02 +0200, Remy Bohmer wrote:
> Hello Steven,
> 
> I was wondering: Is there a preempt-RT-patch planned for 2.6.25?
> I haven't seen one either for any of the 2.6.25-rc kernels at the
> usual place (http://www.kernel.org/pub/linux/kernel/projects/rt/),
> first time in history...
> Am I missing something?


Daniel has done a port, but I think it dropped some archs so its not
complete.


ftp://source.mvista.com/pub/dwalker/rt/patch-2.6.25-rc9-dw1-broken-out.tar.bz2

and updates, possibly:

ftp://source.mvista.com/pub/dwalker/rt/


His bi-sectability changes are pretty key, and I would like to see those
reviewed and incorporated, even if they apply only to x86.

The RT patch queue generally is a mess today. 
Lots of stuff needs to be folded down into the core patches.

The ins and outs of the softirq code need major clean-up.

There are big issues around apic / hardirq threads that we need to
tackle at multiple levels.

(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.

Sven




  reply	other threads:[~2008-05-02 18:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 18:02 Remy Bohmer
2008-05-02 18:34 ` Sven-Thorsten Dietrich [this message]
2008-05-02 18:45   ` Steven Rostedt
2008-05-02 18:54     ` Sven-Thorsten Dietrich
2008-05-02 19:02       ` Steven Rostedt
2008-05-02 19:14         ` Sven-Thorsten Dietrich
2008-05-03  2:44           ` Steven Rostedt
2008-05-05 14:21             ` Daniel Walker
2008-05-05 16:01         ` Daniel Walker
2008-05-05 16:11           ` Steven Rostedt
2008-05-05 16:19             ` Daniel Walker
2008-05-05 16:44               ` Steven Rostedt
2008-05-05 17:04                 ` Daniel Walker
2008-05-05 18:32                   ` Steven Rostedt
2008-05-05 18:58                     ` Daniel Walker
2008-05-05 21:01                       ` Thomas Gleixner
2008-05-05 22:12                         ` Daniel Walker
2008-05-05 23:47                           ` Ingo Molnar
2008-05-06  0:11                             ` Daniel Walker
2008-05-06  1:30                               ` Thomas Gleixner
2008-05-06  1:43                                 ` Daniel Walker
2008-05-06  8:43                               ` Ingo Molnar
2008-05-06 16:01                                 ` Daniel Walker
2008-05-06  0:13                           ` Thomas Gleixner
2008-05-06  1:54                           ` Thomas Gleixner
2008-05-06  2:10                             ` Daniel Walker
2008-05-06  8:19                               ` Thomas Gleixner
2008-05-06 10:40                           ` Steven Rostedt
2008-05-06 16:05                             ` Daniel Walker
2008-05-06 16:32                               ` Steven Rostedt
2008-05-06 17:06                                 ` Daniel Walker
2008-05-06 20:59                                   ` Steven Rostedt
2008-05-05 16:17     ` Daniel Walker
2008-05-05 16:21       ` Steven Rostedt
2008-05-05 16:31         ` Daniel Walker

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=1209753250.25628.34.camel@dd.thebigcorporation.com \
    --to=sven@thebigcorporation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@bohmer.net \
    --cc=rostedt@goodmis.org \
    /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

all inboxes | Powered by JetHome®