| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 26 Feb 2011 16:22:50 +0100 From: Maarten Lankhorst <m.b.lankhorst@...il.com> To: linux-kernel@...r.kernel.org Subject: Taking forward the realtime work 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 -- 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