2.6.14-rc4-rt1
From: | Ingo Molnar <mingo@elte.hu> | |
To: | linux-kernel@vger.kernel.org | |
Subject: | 2.6.14-rc4-rt1 | |
Date: | Tue, 11 Oct 2005 13:14:54 +0200 | |
Cc: | Thomas Gleixner <tglx@linutronix.de>, Steven Rostedt <rostedt@goodmis.org>, dwalker@mvista.com, david singleton <dsingleton@mvista.com> |
i have released the 2.6.14-rc4-rt1 tree, which can be downloaded from the usual place: http://redhat.com/~mingo/realtime-preempt/ lots of fixes all across the spectrum. x64 support and debugging features on x64 should be in a much better shape now. Same for ARM. Ingo Changes since 2.6.14-rc3-rt2: - fix nasty memory corruption and crash caused by PREEMPT_DEBUG's lock tracing functionality (Thomas Gleixner) - ARM updates (Thomas Gleixner) - get rid of bit_spinlock via ->b_state_lock (Steven Rostedt) - ACPI flags mismatch fix (Steven Rostedt) - softlockup false positive fix (Daniel Walker) - robust/PI futex updates (David Singleton) - timesource/ktimer updates (Thomas Gleixner) - pcmcia shutdown hang fix (Steven Rostedt) - fix missing checks for resched - merge to 2.6.14-rc4 - vprintk non-preempt fix - various x64 fixes - netfilter build fixes - various latency tracer fixes - use exact BP stackframes when printing stack-overflow debugging info, if x86 and x64, if possible. - ide-floppy irq flags fix - gameport irq flags fix - stack footprint debugging fixes - small MIPS updates - reduce zlib stack footprint - got rid of the last remains of the tlb-simple stuff - various build fixes of non-PREEMPT_RT preemption models - Kconfig tweak - export tsc_c3_compensate to build a 2.6.14-rc4-rt1 tree, the following patches should be applied: http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.13.tar.bz2 http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6... http://redhat.com/~mingo/realtime-preempt/patch-2.6.14-rc... Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/