On Tue, 2012-10-09 at 14:19 -0400, Steven Rostedt wrote: I applied and tested the backported patches to 3.4-rt. Things look good and will be posting the -rc1 soon. Status for 3.0-rt: > 0000-scsi-qla2xxx-fix-bug-sleeping-function-called-from-invalid-context.patch > 0001-upstream-net-rt-remove-preemption-disabling-in-netisched-better-debug-output-for-might-sleep.patch f_rx.patch The above two have been applied to both 3.0-rt and 3.4-rt previously. > 0002-random-make-it-work-on-rt.patch The above has been applied to 3.4-rt but is not applicable to 3.0-rt, as the add_interrupt_randomness() does not exist. > 0003-softirq-init-softirq-local-lock-after-per-cpu-section-is-set-up.patch For 3.0-rt the softirq_early_init() comes after the printk banner, which is after per cpu data has been set up. But for consistency, I made this patch moved to before the banner in the same location as 3.4-rt+ is. > 0004-mm-slab-fix-potential-deadlock.patch > 0005-mm-page-alloc-use-local-lock-on-target-cpu.patch > 0006-rt-rw-lockdep-annotations.patch The above applied to 3.0-rt with no issues. * sched-better-debug-output-for-might-sleep.patch Had slight conflicts, but trivial fix. > 0007-stomp-machine-deal-clever-with-stopper-lock.patch With this one, things have changed quite a bit. I'll take a deeper look at what you did and figure out how this applies to v3.0-rt. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
