public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Taking forward the realtime work
Date: Sat, 26 Feb 2011 16:22:50 +0100	[thread overview]
Message-ID: <4D691ACA.9090405@gmail.com> (raw)

Hi all,

After digging through the -rt patchset again I wanted to take it forward 
to the current kernel, so far I didn't to get much work done as the code 
seems to be kinda invasive, even with a lot of the things already in 
mainline. However a lot of things in the -rt patch seem to no longer be 
needed, since softirqs are merged, the BKL is gone, and there's a patch 
set out to make mm preemptible.

I've started testing from the mm-preempt patchset, and it seems to boot, 
but now that I'm actually looking at the -rt patchset diff from 
v2.6.33.7 it's not that trivial to port forward, so I'm looking for 
help. Blindly trying to apply the diff forward 6 versions will not work, 
so I'm looking at how to add the patches in such a way that each change 
is done in a logical order, in such a way preferably that at each point 
the kernel is bootable. I understand that for -rt there will be a few 
commits for which that won't be possible, but it seems to me the amount 
of work needed to get -rt working isn't as big any more as it used to be.

Note: There's no guarantee I'll be able to pull it off, but there's this 
itch I need to get rid of. ;)

Cheers,
Maarten

             reply	other threads:[~2011-02-26 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 15:22 Maarten Lankhorst [this message]
2011-02-28 20:42 ` Taking forward the realtime work Thomas Gleixner

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=4D691ACA.9090405@gmail.com \
    --to=m.b.lankhorst@gmail.com \
    --cc=linux-kernel@vger.kernel.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