Linux Real Time Users
[Prev Page][Next Page]
- 2.6.24.2-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Bill Huey (hui)" <bill.huey@xxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Bill Huey (hui)" <bill.huey@xxxxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH [RT] 08/14] add a loop counter based timeout mechanism
- From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
- Re: [PATCH [RT] 08/14] add a loop counter based timeout mechanism
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH [RT] 10/14] adjust pi_lock usage in wakeup
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH [RT] 08/14] add a loop counter based timeout mechanism
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH [RT] 11/14] optimize the !printk fastpath through the lock acquisition
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH [RT] 10/14] adjust pi_lock usage in wakeup
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH [RT] 08/14] add a loop counter based timeout mechanism
- From: Andi Kleen <ak@xxxxxxx>
- Re: [PATCH [RT] 11/14] optimize the !printk fastpath through the lock acquisition
- From: Andi Kleen <ak@xxxxxxx>
- Re: [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 14/14] sysctl for runtime-control of lateral mutex stealing
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 13/14] allow rt-mutex lock-stealing to include lateral priority
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 12/14] remove the extra call to try_to_take_lock
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 11/14] optimize the !printk fastpath through the lock acquisition
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 10/14] adjust pi_lock usage in wakeup
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 09/14] adaptive mutexes
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 08/14] add a loop counter based timeout mechanism
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 07/14] adaptive real-time lock support
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 06/14] optimize rt lock wakeup
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 05/14] rearrange rt_spin_lock sleep
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 04/14] disable PREEMPT_SPINLOCK_WAITERS when x86 ticket/fifo spins are in use
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 03/14] x86: FIFO ticket spinlocks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 02/14] spinlock: make preemptible-waiter feature a specific config option
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 00/14] RFC - adaptive real-time locks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH [RT] 01/14] spinlocks: fix preemption feature when PREEMPT_RT is enabled
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Markers: multi-probe locking fun (was: Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II)
- From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
- Re: sched_yield() needed for pthread_cond_signal(..) to work?
- From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
- Re: sched_yield() needed for pthread_cond_signal(..) to work?
- From: Michal Schmidt <mschmidt@xxxxxxxxxx>
- Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: sched_yield() needed for pthread_cond_signal(..) to work?
- From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
- Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: sched_yield() needed for pthread_cond_signal(..) to work?
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Re: cyclictest?
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- sched_yield() needed for pthread_cond_signal(..) to work?
- From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
- Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II
- From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
- Re: [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II
- From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
- [RT] 2.6.24 - stuck in serial8250_console_write
- From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
- patch-2.6.24-rt1 : ARM doesn't select HAVE_MCOUNT
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Re: [PATCH -rt] ARM: compile fix for event tracing
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Re: [PATCH 2.6.24-rt1] SMC91x: Use special_lock when CONFIG_PREEMPT_[HARD|SOFT]IRQS
- From: Nicolas Pitre <nico@xxxxxxx>
- Lttng for 2.6.24-rt1 ?
- From: "Daniel Schnell" <daniel.schnell@xxxxxxxxx>
- Re: [PATCH 2.6.24-rt1] timer:fix build warning in timer.c
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH 2.6.24-rt1] timer:fix build warning in timer.c
- From: Shi Weihua <shiwh@xxxxxxxxxxxxxx>
- [PATCH 2.6.24-rt1] SMC91x: Use special_lock when CONFIG_PREEMPT_[HARD|SOFT]IRQS
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: [PATCH 1/2] add task migration_disable critical section
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH 1/2] add task migration_disable critical section
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH 1/2] add task migration_disable critical section
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 0/2] migration disabled critical sections
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 2/2] fix cpus_allowed settings
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Soft lockup when running large iterations of gtod
- From: Ankita Garg <ankita@xxxxxxxxxx>
- Re: IBM test question
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Re: IBM test question
- From: Esben Nielsen <nielsen.esben@xxxxxxxxxxxxxx>
- Re: Soft lockup when running large iterations of gtod
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Re: Soft lockup when running large iterations of gtod
- From: Ankita Garg <ankita@xxxxxxxxxx>
- Re: IBM test question
- From: Sébastien Dugué <sebastien.dugue@xxxxxxxx>
- Soft lockup when running large iterations of gtod
- From: Ankita Garg <ankita@xxxxxxxxxx>
- Re: IBM test question
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Re: IBM test question
- From: Sébastien Dugué <sebastien.dugue@xxxxxxxx>
- IBM test question
- From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
- Re: cpuisol: CPU isolation extensions (take 2)
- From: Max Krasnyanskiy <maxk@xxxxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: Daniel Walker <dwalker@xxxxxxxxxxxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: Daniel Walker <dwalker@xxxxxxxxxxxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: Max Krasnyansky <maxk@xxxxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: CPU hotplug and IRQ affinity with 2.6.24-rt1
- From: Daniel Walker <dwalker@xxxxxxxxxxxxxxxxxxx>
- Re: 2.6.24-rt1 SSttrraannggee keyboard behaviour
- From: "Uli Brueggemann" <uli.brueggemann@xxxxxxxxx>
- Re: 2.6.24-rt1 SSttrraannggee keyboard behaviour
- From: Clark Williams <williams@xxxxxxxxxx>
- 2.6.24-rt1 SSttrraannggee keyboard behaviour
- From: "Uli Brueggemann" <uli.brueggemann@xxxxxxxxx>
- Re: uvesafb + 2.6.24-rt
- From: Thomas <gimpel@xxxxxxxxxxxxxxxx>
- uvesafb + 2.6.24-rt
- From: Thomas <gimpel@xxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: X86 Pentium M platform troubles at low temperatures
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- Re: how does Real-time Linux and (Xen) Virtualization work together?
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- Re: X86 Pentium M platform troubles at low temperatures
- From: "Jim Beck" <4805455@xxxxxxxxx>
- how does Real-time Linux and (Xen) Virtualization work together?
- From: Gautam Thaker <ghthaker@xxxxxxxxx>
- [PATCH] fix workqueue plist init to include a spinlock
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: [PATCH -v2 4/7] RT overloaded runqueues accounting
- From: Paul Jackson <pj@xxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Stefan Monnier <monnier@xxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Esben Nielsen <nielsen.esben@xxxxxxxxxxxxxx>
- Re: 2.6.24-rt1
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.24-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rt1
- From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
- X86 Pentium M platform troubles at low temperatures
- From: "Jim Beck" <4805455@xxxxxxxxx>
- Re: 2.6.24-rt1
- From: Dragan Noveski <perodog@xxxxxxx>
- 2.6.24-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: Real-time Linux Installation Verification and Benchmark
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Real-time Linux Installation Verification and Benchmark
- From: Markus Mathes <mathes@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: Use the RT Latency Trace? - LET ME KNOW!
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Use the RT Latency Trace? - LET ME KNOW!
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- AW: AW: How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: "Lampersperger Andreas" <lampersperger.andreas@xxxxxxxxxxxxx>
- Re: AW: How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
- AW: How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: "Lampersperger Andreas" <lampersperger.andreas@xxxxxxxxxxxxx>
- Re: How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
- How to enable HPET on an 2.6.23.9-rt12 with Intel ICH2
- From: "Lampersperger Andreas" <lampersperger.andreas@xxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Esben Nielsen <nielsen.esben@xxxxxxxxxxxxxx>
- Re: Why not creating a GIT RT tree ?
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Would like to run better stress test.
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Would like to run better stress test.
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc8-rt1
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- 2.6.24-rc8-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [BUG] Oops while running Specjbb on -rt kernel
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt3
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc7-rt3
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt3
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: "S.Çağlar Onur" <caglar@xxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: "S.Çağlar Onur" <caglar@xxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Valdis.Kletnieks@xxxxxx
- 2.6.24-rc7-rt3
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Valdis.Kletnieks@xxxxxx
- Re: 2.6.24-rc7-rt2
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mike Galbraith <efault@xxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mike Galbraith <efault@xxxxxx>
- Re: 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz()
- From: Mike Galbraith <efault@xxxxxx>
- Re: 2.6.24-rc7-rt2
- From: "S.Çağlar Onur" <caglar@xxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt2
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- 2.6.24-rc7-rt2
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH] fix up leak_check calls
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: "S.Çağlar Onur" <caglar@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Pavel Machek <pavel@xxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mike Galbraith <efault@xxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mike Galbraith <efault@xxxxxx>
- Re: 2.6.24-rc7-rt1
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mike Galbraith <efault@xxxxxx>
- [BUG] Oops while running Specjbb on -rt kernel
- From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- Re: 2.6.24-rc7-rt1: macro "put_cpu_var" passed 2 arguments, but takes just 1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: 2.6.24-rc7-rt1: macro "put_cpu_var" passed 2 arguments, but takes just 1
- From: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx>
- 2.6.24-rc7-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH PREEMPT_RT] Compilation fix for PPC
- From: Sripathi Kodi <sripathik@xxxxxxxxxx>
- Re: [patch 2.6.24-rc7-rt1-pre1] per_cpu__ppc64_tlb_batch is only for 64 bit
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: preempt_max_latency_us undeclared for latency tracer
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [patch 2.6.24-rc7-rt1-pre1] per_cpu__ppc64_tlb_batch is only for 64 bit
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: lost patch for mpc52xx spinlock
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- preempt_max_latency_us undeclared for latency tracer
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- [patch 2.6.24-rc7-rt1-pre1] per_cpu__ppc64_tlb_batch is only for 64 bit
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- lost patch for mpc52xx spinlock
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: cyclictest?
- From: Darren Hart <dvhltc@xxxxxxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: cyclictest?
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: cyclictest?
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: cyclictest?
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- cyclictest?
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- need RT Video card recommendation
- From: "Jon Clifton" <J_Clifton@xxxxxxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
- High latencies on MPC5200 with patch-2.6.24-rc5-rt1
- From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
- [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing - Ver II
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- [PATCH 1/2] Markers Implementation for RCU Preempt Tracing - Ver II
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- [PATCH 0/2] Markers Implementation for RCU Tracing - Ver II
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- rt-related bug?
- From: Tim Blechmann <tim@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: Question: RT patch and CFS patch ?
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: __get_cpu_var() called from a preempt-unsafe context in __rcu_preempt_unboost() ?
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- __get_cpu_var() called from a preempt-unsafe context in __rcu_preempt_unboost() ?
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
- Re: neigh: timer & !nud_in_timer
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Nicholas Miell <nmiell@xxxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Ingo Molnar <mingo@xxxxxxx>
- Question: RT patch and CFS patch ?
- From: Andrzej Walczak <awalczak@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: fche@xxxxxxxxxx (Frank Ch. Eigler)
- [ANNOUNCE] [LTP] The Linux Test Project has been Released for DECEMBER 2007
- From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: Sripathi Kodi <sripathik@xxxxxxxxxx>
- Re: [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: Ingo Molnar <mingo@xxxxxxx>
- [PATCH 2/2] Markers Implementation for Preempt RCU Boost Tracing
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- [PATCH 1/2] Markers Implementation for RCU Preempt Tracing
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- [PATCH 0/2] Markers Implementation for RCU Tracing
- From: "K. Prasad" <prasad@xxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- Re: Fwd: -rt and PowerPC
- From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
- Re: yum repository for kernel-rt ?
- From: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
- Re: yum repository for kernel-rt ?
- From: "Javier Sanz" <jsanza@xxxxxxxxx>
- Fwd: -rt and PowerPC
- From: Sripathi Kodi <sripathik@xxxxxxxxxx>
- yum repository for kernel-rt ?
- From: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
- [PATCH] Re: loadavg vs loadavgrt
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: loadavg vs loadavgrt
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Re: loadavg vs loadavgrt
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: loadavg vs loadavgrt
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- PPC64 doesn't compile with CONFIG_SMP=n
- From: Egor Starkov <estarkov@xxxxxxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- neigh: timer & !nud_in_timer
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [patch 2/3] Enable setting of IRQ-thread priorities from kernel cmdline (repost:CC to LKML)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- loadavg vs loadavgrt
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line (repost:CC to LKML)
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line (repost:CC to LKML)
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: [patch 2/3] Enable setting of IRQ-thread priorities from kernel cmdline (repost:CC to LKML)
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. (repost:CC to LKML)
- From: Remy Bohmer <linux@xxxxxxxxxx>
- [patch 2/3] Enable setting of IRQ-thread priorities from kernel cmdline (repost:CC to LKML)
- From: Remy Bohmer <linux@xxxxxxxxxx>
- [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line (repost:CC to LKML)
- From: Remy Bohmer <linux@xxxxxxxxxx>
- [patch 0/3] add kernel-cmdline support for interrupt thread priorities (repost:CC to LKML)
- From: Remy Bohmer <linux@xxxxxxxxxx>
- Re: [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line
- From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
- 2.6.23.11-rt14
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline.
- From: Remy Bohmer <remy@xxxxxxxxxx>
- [patch 2/3] Enable setting of IRQ-thread priorities from kernel cmdline
- From: Remy Bohmer <remy@xxxxxxxxxx>
- [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line
- From: Remy Bohmer <remy@xxxxxxxxxx>
- [patch 0/3] add kernel-cmdline support for interrupt threads priorities
- From: Remy Bohmer <remy@xxxxxxxxxx>
- [Question]: Regarding time stability, NTP, clock adjustments
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH] sched: dynamically update the root-domain span/online maps
- From: Steven Rostedt <srostedt@xxxxxxxxxx>
- Re: [PATCH] sched: dynamically update the root-domain span/online maps
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH] sched: dynamically update the root-domain span/online maps
- From: Steven Rostedt <srostedt@xxxxxxxxxx>
- [PATCH] sched: dynamically update the root-domain span/online maps
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Haavard Skinnemoen <hskinnemoen@xxxxxxxxx>
- Re: [PATCH][RT] 2.6.24-rc5-rt1 drivers/dma/ioat_dma.c compile fix
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH][RT] 2.6.24-rc5-rt1 drivers/dma/ioat_dma.c compile fix
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- 2.6.24-rc5-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [RFC PATCH 2/6] Preempt-RCU: Reorganize RCU code into rcuclassic.c and rcupdate.c
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH 2/6] Preempt-RCU: Reorganize RCU code into rcuclassic.c and rcupdate.c
- From: Johannes Weiner <hannes-kernel@xxxxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Using CONFIG_FUNCTION_TRACE
- From: Darren Hart <dvhltc@xxxxxxxxxxxxxxxxxx>
- 2.6.24-rc2-rt1 build failure: mod_unreg_security
- From: Darren Hart <dvhltc@xxxxxxxxxxxxxxxxxx>
- Re: 2.6.23.9-rt13
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: 2.6.23.9-rt13
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- Re: [RFC PATCH 6/6] Preempt-RCU: Update RCU Documentation.
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [RFC PATCH 6/6] Preempt-RCU: Update RCU Documentation.
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Andrew Victor" <avictor.za@xxxxxxxxx>
- [RFC PATCH 6/6] Preempt-RCU: Update RCU Documentation.
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 5/6] Preempt-RCU: CPU Hotplug handling
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 4/6] Preempt-RCU: Implementation
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 3/6] Preempt-RCU: Fix rcu_barrier for preemptive environment
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 2/6] Preempt-RCU: Reorganize RCU code into rcuclassic.c and rcupdate.c
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 1/6] Preempt-RCU: Use softirq instead of tasklets for RCU
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- [RFC PATCH 0/6] RCU: Preemptible-RCU
- From: Gautham R Shenoy <ego@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: 2.6.23.9-rt13
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- 2.6.23.9-rt13
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.8-rt11, tasks freezing
- From: "Florent BOUDET" <fboudet@xxxxxxxxxxxx>
- Re: [PATCH RT] add pending in fasteoi for IOAPIC hack
- From: Jon Masters <jcm@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH RT] Revert Softdisable for simple irqs.
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH RT] add pending in fasteoi for IOAPIC hack
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH RT] Revert Softdisable for simple irqs.
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH -rt] cycles_to_usecs rounding fix
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH] handle IRQ_PENDING for simple irq handler
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH RT] Revert Softdisable for simple irqs.
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- [PATCH] handle IRQ_PENDING for simple irq handler
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH RT] Revert Softdisable for simple irqs.
- From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
- [PATCH RT] Revert Softdisable for simple irqs.
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH -rt] Add wakeup timing to expose /proc/preempt_max_latency
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- [PATCH -rt] preempt_max_latency to microseconds
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- [PATCH/RFC -rt] local_bh_enable() is safe for irqs_disabled()
- From: Kevin Hilman <kevin@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Andrew Victor" <avictor.za@xxxxxxxxx>
- Re: [PATCH]: Atmel Serial Console interrupt handler splitup
- From: David Brownell <david-b@xxxxxxxxxxx>
- [PATCH]: Atmel Serial Console interrupt handler splitup
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- [PATCH for 2.6.24rc2-rt1] Use real time pcp locking for page draining during cpu unplug
- From: Andi Kleen <ak@xxxxxxx>
- Re: Problems with cyclictest and ps
- From: Florian Boelstler <euphoria@xxxxxxxx>
- Re: [PATCH Latency Tracer] don't panic on failed bootmem alloc
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: Problems with cyclictest and ps
- From: "Phil K." <binutz@xxxxxxxxx>
- Re: Problems with cyclictest and ps
- From: "Phil K." <binutz@xxxxxxxxx>
- [PATCH Latency Tracer] don't panic on failed bootmem alloc
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Problems with cyclictest and ps
- From: Florian Boelstler <euphoria@xxxxxxxx>
- Re: Problems with cyclictest and ps
- From: "K.R. Foley" <kr@xxxxxxxxxx>
- Problems with cyclictest and ps
- From: "Phil K." <binutz@xxxxxxxxx>
- Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: Ingo Molnar <mingo@xxxxxxx>
- [PATCH] ARM: OMAP: use edge/level handlers from generic IRQ framework
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- [PATCH] Generic IRQ: Add unlocked version of set_irq_handler()
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- [PATCH] ARM: OMAP: Clear level-triggered GPIO interrupts in unmask hook
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- [PATCH] ARM: OMAP: Fix GPIO IRQ unmask
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- [PATCH/RFC] OMAP GPIO IRQ rework for generic IRQ subsystem
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: Generic IRQs: proper edge/level via irq_chip->set_type hook
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 2/3] Subject: SCHED - Only balance our RT tasks within our root-domain
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 1/3] Subject: SCHED - Add sched-domain roots
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 0/3] RT balance v7a
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Generic IRQs: proper edge/level via irq_chip->set_type hook
- From: David Brownell <david-b@xxxxxxxxxxx>
- Generic IRQs: proper edge/level via irq_chip->set_type hook
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: [PATCH 00/23] RT balance v7
- From: Gregory Haskins <gregory.haskins.ml@xxxxxxxxx>
- Re: [PATCH 00/23] RT balance v7
- From: Ingo Molnar <mingo@xxxxxxx>
- [PATCH 23/23] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 22/23] Subject: SCHED - Only balance our RT tasks within our root-domain
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 21/23] Subject: SCHED - Add sched-domain roots
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 20/23] Subject: SCHED - balance RT tasks no new wake up
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 19/23] Subject: SCHED - Optimize out cpu_clears
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 18/23] Subject: SCHED - Optimize cpu search with hamming weight
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 17/23] Subject: SCHED - restore the migratable conditional
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 16/23] Subject: SCHED - Avoid overload
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 15/23] Subject: SCHED - Optimize rebalancing
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 14/23] Subject: SCHED - Optimize our cpu selection based on topology
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 13/23] Subject: SCHED - Pre-route RT tasks on wakeup
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 12/23] Subject: SCHED - Allow current_cpu to be included in search
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 11/23] Subject: SCHED - Break out the search function
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 10/23] Subject: SCHED - Remove some CFS specific code from the wakeup path of RT tasks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 09/23] Subject: SCHED - Consistency cleanup for this_rq usage
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 08/23] Subject: SCHED - Cache cpus_allowed weight for optimizing migration
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 07/23] Subject: SCHED - disable CFS RT load balancing.
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 06/23] Subject: SCHED - wake up balance RT
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 05/23] Subject: SCHED - pull RT tasks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 04/23] Subject: SCHED - RT overloaded runqueues accounting
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 03/23] Subject: SCHED - push RT tasks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 02/23] Subject: SCHED - track highest prio queued on runqueue
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 01/23] Subject: SCHED - Add rt_nr_running accounting
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 00/23] RT balance v7
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: [PATCH -rt] ARM: compile fix for event tracing
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH -rt] ARM: compile fix for event tracing
- From: Kevin Hilman <khilman@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
- [PATCH 4/4] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 3/4] Subject: SCHED - Only balance our RT tasks within our root-domain
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 2/4] Subject: SCHED - Add sched-domain roots
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 1/4] Subject: SCHED - Make the wake-up priority a config option
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 0/4] more RT balancing enhancements v6b
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Priorities of IRQ handlers
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Re: 2.6.23.8-rt11, tasks freezing
- From: Juuso Alasuutari <juuso.alasuutari@xxxxxxxxx>
- Re: 2.6.23.8-rt11, tasks freezing
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- AVR32
- From: DM <dm.n9107@xxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: 2.6.23.8-rt11, tasks freezing
- From: Juuso Alasuutari <juuso.alasuutari@xxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: rt mutex priority boost
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: rt mutex priority boost
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: rt mutex priority boost
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: rt mutex priority boost
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- Re: rt mutex priority boost
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Priorities of IRQ handlers
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
- [ANNOUNCE] Preempt-test v4 released
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: Priorities of IRQ handlers
- From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: rt mutex priority boost
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- 2.6.23.9-rt12
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Priorities of IRQ handlers
- From: "K.R. Foley" <kr@xxxxxxxxxx>
- Re: rt mutex priority boost
- From: Luís Henriques <lhenriques@xxxxxxxxxxx>
- rt mutex priority boost
- From: "Peter W. Morreale" <pmorreale@xxxxxxxxxx>
- Re: Priorities of IRQ handlers
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: Priorities of IRQ handlers
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: updated ketchup script
- From: Michal Schmidt <mschmidt@xxxxxxxxxx>
- Re: updated ketchup script
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Priorities of IRQ handlers
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: bug in change from rt preempt 2.6.20 to 2.6.21? - energyxt2 problems.
- From: James Stone <jamesmstone@xxxxxxxxx>
- updated ketchup script
- From: Michal Schmidt <mschmidt@xxxxxxxxxx>
- Re: 2.6.23.8-rt11, tasks freezing
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- 2.6.23.8-rt11, tasks freezing
- From: Juuso Alasuutari <juuso.alasuutari@xxxxxxxxx>
- [PREEMPT_RT] LOCK_STAT and kexec: general protection fault
- From: Sripathi Kodi <sripathik@xxxxxxxxxx>
- Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix
- From: trem <tremyfr@xxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: David Chinner <dgc@xxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix
- From: "Nelson, Shannon" <shannon.nelson@xxxxxxxxx>
- [BUG on PREEMPT_RT, 2.6.23.1-rt5] in rt-mutex code and signals
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix
- From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
- 2.6.24-rc2-rt1 - inet-hash-bits-ipv6-fix.patch
- From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.24-rc2-rt1
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- 2.6.24-rc2-rt1
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: Cyclictest
- From: "K.R. Foley" <kr@xxxxxxxxxx>
- Re: Cyclictest
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Cyclictest
- From: "K.R. Foley" <kr@xxxxxxxxxx>
- latency trace
- From: "Kaya, Sinan" <sinan.kaya@xxxxxxxxxxx>
- [PATCH] RT: convert cpupri spinlock_t to raw_spinlock_t
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH] RT: Fix a bug for properly setting the priority on rt-dequeue
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
- Re: syslog(3) blocks when local socket is full
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: syslog(3) blocks when local socket is full
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: syslog(3) blocks when local socket is full
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: syslog(3) blocks when local socket is full
- From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
- syslog(3) blocks when local socket is full
- From: John Sigler <linux.kernel@xxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: How to use latency trace
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: How to use latency trace
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- IBM rt-tests-0.6 snapshot
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Bernhard Kuhn <kuhn@xxxxxxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Luís Henriques <lhenriques@xxxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Bernhard Kuhn <kuhn@xxxxxxxxxxxxxx>
- Log from 2.6.23.1-rt11
- From: Andrzej Walczak <awalczak@xxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Luís Henriques <lhenriques@xxxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Bernhard Kuhn <kuhn@xxxxxxxxxxxxxx>
- Re: Priority Ceiling for SMP?
- From: Luís Henriques <lhenriques@xxxxxxxxxxx>
- Priority Ceiling for SMP?
- From: Bernhard Kuhn <kuhn@xxxxxxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: [RFC] [PATCH] powerpc Re: [announce] IBM RT Test Cases v.0.3
- From: Tsutomu OWA <tsutomu.owa@xxxxxxxxxxxxx>
- lockdep with 2.6.23.1 - rt10
- From: "Kaya, Sinan" <sinan.kaya@xxxxxxxxxxx>
- cyclic test results on 8 way (2.6.23.1-rt7 through 2.6.23.1-rt11)
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH] RT: fix uniprocessor build issue with new scheduler enhancements
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
- Re: 2.6.23.1-rt9 (and others)
- From: Dragan Noveski <perodog@xxxxxxx>
- 2.6.23.1-rt9 (and others)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: How to use latency trace
- From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
- [PATCH 4/8] RT: Allow current_cpu to be included in search
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 7/8] RT: Optimize rebalancing
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 6/8] RT: Optimize our cpu selection based on topology
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 2/8] RT: Remove some CFS specific code from the wakeup path of RT tasks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 3/8] RT: Break out the search function
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 0/8] RT: scheduler migration/wakeup enhancements
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 2/8] RT: Remove some CFS specific code from the wakeup path of RT tasks
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 1/8] RT: Consistency cleanup for this_rq usage
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 8/8] RT: Use a 2-d bitmap for searching lowest-pri CPU
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 7/8] RT: Optimize rebalancing
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 1/8] RT: Consistency cleanup for this_rq usage
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 5/8] RT: Pre-route RT tasks on wakeup
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 5/8] RT: Pre-route RT tasks on wakeup
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 6/8] RT: Optimize our cpu selection based on topology
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 4/8] RT: Allow current_cpu to be included in search
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 0/8] RT: scheduler migration/wakeup enhancements
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 3/8] RT: Break out the search function
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 8/8] RT: Use a 2-d bitmap for searching lowest-pri CPU
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: thread load balancing on dual CPU Multicore AMD64 system
- From: "Hillier, Gernot" <gernot.hillier@xxxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Gabriel C <nix.or.die@xxxxxxxxxxxxxx>
- Re: thread load balancing on dual CPU Multicore AMD64 system
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: How to use latency trace
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: thread load balancing on dual CPU Multicore AMD64 system
- From: Gernot Hillier <gernot.hillier@xxxxxxxxxxx>
- How to use latency trace
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: old rt patches
- From: "Remy Bohmer" <linux@xxxxxxxxxx>
- Re: [RFC] [PATCH] powerpc Re: [announce] IBM RT Test Cases v.0.3
- From: Darren Hart <dvhltc@xxxxxxxxxx>
- Re: old rt patches
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: old rt patches
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- Re: old rt patches
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- old rt patches
- From: "Jaswinder Singh" <jaswinderlinuxrt@xxxxxxxxx>
- kernel linux 2.6.23.1-rt4 Musix (Debian/ETCH)
- From: Marcos Guglielmetti <marcospcmusica@xxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: 2.6.23.1-rt5 rtc lost interrupt
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt5 rtc lost interrupt
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- 2.6.23.1-rt5 rtc lost interrupt
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: Is it a stupid question?
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
- Kexec and rt kernel
- From: "Kaya, Sinan" <sinan.kaya@xxxxxxxxxxx>
- Is it a stupid question?
- From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH -rt] remove in_interrupt() BUG_ON in exit path
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH -rt] remove in_interrupt() BUG_ON in exit path
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: [PATCH -rt] remove in_interrupt() BUG_ON in exit path
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH -rt] remove in_interrupt() BUG_ON in exit path
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Rui Nuno Capela <rncbc@xxxxxxxxx>
- SMP latency
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Daniel Walker <dwalker@xxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Rui Nuno Capela <rncbc@xxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
- From: Rui Nuno Capela <rncbc@xxxxxxxxx>
- 2.6.23.1-rt5
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- CONFIG_CRITICAL_IRQSOFF_TIMING
- From: Gerrit Binnenmars <gerritbinnenmars@xxxxxxxxxx>
- Re: 2.6.23-rt4 (was 2.6.23-rt1 trouble)
- From: Rui Nuno Capela <rncbc@xxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23-rt4 (was 2.6.23-rt1 trouble)
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: 2.6.23.1-rt4
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: trem <tremyfr@xxxxxxxx>
- Re: 2.6.23-rt4 (was 2.6.23-rt1 trouble)
- From: Rui Nuno Capela <rncbc@xxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH] Don't disable preemption in exception handlers without IST
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: 2.6.23.1-rt4
- From: Dragan Noveski <perodog@xxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Ingo Molnar <mingo@xxxxxxx>
- [PATCH] Don't disable preemption in exception handlers without IST
- From: Andi Kleen <ak@xxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Mike Galbraith <efault@xxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: "Jaswinder Singh" <jaswinderlinux@xxxxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Mike Galbraith <efault@xxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Mike Galbraith <efault@xxxxxx>
- Re: [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
- [2.6.23-rt3] NMI watchdog trace of deadlock
- From: Mike Galbraith <efault@xxxxxx>
- 2.6.23.1-rt4
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH 2/2] RT: Cache cpus_allowed weight for optimizing migration
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- [PATCH 2/2] RT: Cache cpus_allowed weight for optimizing migration
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- [PATCH 1/2] RT: cleanup some push-rt logic
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
- Re: Possible bug in 23rt3 preempt-irqs-core.patch
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH] RT: Cache cpus_allowed weight for optimizing migration
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Re: [PATCH] RT: Cache cpus_allowed weight for optimizing migration
- From: Gregory Haskins <ghaskins@xxxxxxxxxx>
[Index of Archives]
[RT Stable]
[Kernel Announce]
[IETF Annouce]
[Security]
[Netfilter]
[Linux ATA RAID]
[Bugtraq]
