Linux Real Time Users

• Thread Index

• Re: [RT] [RFC] simple SMI detector
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Spinlock recursion detected on preempt-RT and interrupt handler set_type code
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Jon Masters <jcm@xxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [RT] [RFC] simple SMI detector
  • From: Lee Revell <rlrevell@xxxxxxxxxxx>
• [RT] [RFC] simple SMI detector
  • From: Jon Masters <jcm@xxxxxxxxxx>
• RE: 2.6.26.8-rt13
  • From: Lampersperger Andreas <lampersperger.andreas@xxxxxxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Esben Nielsen <esn@xxxxxxxxx>
• Re: [RT] [git pull] updates for rt/sched
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT] [git pull] updates for rt/sched
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• RE: 2.6.24.7-rt26 and 2.6.26.8-rt13
  • From: Lampersperger Andreas <lampersperger.andreas@xxxxxxxxxxxxx>
• RE: 2.6.24.7-rt26 and 2.6.26.8-rt13
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• RE: 2.6.24.7-rt26 and 2.6.26.8-rt13
  • From: Lampersperger Andreas <lampersperger.andreas@xxxxxxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Pradyumna Sampath <pradysam@xxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: Which version of preempt_realtime to use?
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Which version of preempt_realtime to use?
  • From: Esben Nielsen <esn@xxxxxxxxx>
• Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: kristrev@xxxxxxxxx
• Re: [RT git pull] fixes for rt/sched
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RT git pull] fixes for rt/sched
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RT git pull] fixes for rt/sched
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: "Ilpo Järvinen" <ilpo.jarvinen@xxxxxxxxxxx>
• Re: BUG: using smp_processor_id() in preemptible
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: Andreas Petlund <apetlund@xxxxxxxxx>
• 2.6.24.7-rt26 and 2.6.26.8-rt13
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.24.7-rt25 and 2.6.26.8-rt12
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [LAU] [PATCH] [RT] tasklets: fix typo in tasklet_hi_action
  • From: Fernando Lopez-Lezcano <nando@xxxxxxxxxxxxxxxxxx>
• [PATCH] fix documentation of thread priorities for option -p to cyclictest
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH] [RT] tasklets: fix typo in tasklet_hi_action
  • From: Adam Sampson <ats@xxxxxxxxx>
• Re: Specialization project, Real-Time Scheduling
  • From: "MinChan Kim" <minchan.kim@xxxxxxxxx>
• Specialization project, Real-Time Scheduling
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: 2.6.24.7-rt25 and 2.6.26.8-rt12
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.24.7-rt25 and 2.6.26.8-rt12
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.24.7-rt25 and 2.6.26.8-rt12
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• 4gb himem bug? 2.6.28-rt12
  • From: "Javier Sanz" <jsanza@xxxxxxxxx>
• processor isolation inquiry
  • From: Mark Hounschell <dmarkh@xxxxxxxxxx>
• Network packet reordering.
  • From: Amir Aharon <amira@xxxxxxxxx>
• Re: [patch 1/7] ftrace: fix task state printout
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• 2.6.24.7-rt25 and 2.6.26.8-rt12
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [patch 1/7] ftrace: fix task state printout
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 7/7] rtmutex: prevent missed wakeups
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 6/7] rtmutex: remove useless schedule enforcement
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 4/7] rtmutex: unify state manipulation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 5/7] rtmutex: remove uber optimization
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 3/7] rtmutex: remove unused variable
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 1/7] ftrace: fix task state printout
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 2/7] sched: remove useless nointeractive state
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 0/7] 2.6.24.7-rt24 bugfixes V2
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [patch 1/7] ftrace: fix task state printout
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [patch 4/7] rtmutex: unify state manipulation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [patch 4/7] rtmutex: unify state manipulation
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [patch 1/7] ftrace: fix task state printout
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• [patch 7/7] rtmutex: prevent missed wakeups
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 6/7] rtmutex: remove useless schedule enforcement
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 5/7] rtmutex: remove uber optimization
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 4/7] rtmutex: unify state manipulation
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 3/7] rtmutex: remove unused variable
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 1/7] ftrace: fix task state printout
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 2/7] sched: remove useless nointeractive state
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [patch 0/7] 2.6.24.7-rt24 bugfixes
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: rt-sources 2.6.26.6-rt11 fails to make
  • From: "Gilles.Carry" <Gilles.Carry@xxxxxxxxxxxx>
• rt-sources 2.6.26.6-rt11 fails to make
  • From: "Audiodef" <damien@xxxxxxxxxxxx>
• Creating the RT git tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH][RT] - fix 32-bit breakage on rt/threadirqs branch
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
• [PATCH] [RT] preempt_disable_rt for CONFIG_PREEMPT_RT
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• [PATCH] [RT] avoid preemption in memory controller code
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• 2.6.24.7-rt24
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH][RT] Compile-time fix.
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH][RT] Compile-time fix.
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH][RT] Compile-time fix.
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH][RT] lock.h: fix spelling of contended
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH][RT] Compile-time fix.
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH][RT] lock.h: fix spelling of contended
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] The -rt git tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] The -rt git tree
  • From: "Remy Bohmer" <linux@xxxxxxxxxx>
• Re: [ANNOUNCE] The -rt git tree
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: [ANNOUNCE] The -rt git tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] The -rt git tree
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• [ANNOUNCE] The -rt git tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: Li Zefan <lizf@xxxxxxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• Re: [PATCH] [RT] avoid preemption in memory controller code
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] [RT] avoid preemption in memory controller code
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• BUG: using smp_processor_id() in preemptible
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• [PATCH v3 4/4] sched: use highest_prio.next to optimize pull operations
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v3 3/4] sched: use highest_prio.curr for pull threshold
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v3 2/4] sched: track the next-highest priority on each runqueue
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v3 1/4] sched: cleanup inc/dec_rt_tasks
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v3 0/4] sched: track next-highest priority
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/4] sched: track the next-highest priority on each runqueue
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 2/4] sched: track the next-highest priority on each runqueue
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 4/4] sched: use highest_prio.next to optimize pull operations
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 3/4] sched: use highest_prio.curr for pull threshold
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 0/4] sched: track next-highest priority
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 1/4] sched: cleanup inc/dec_rt_tasks
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] sched: track next-highest priority (was "Series short discription")
  • From: Gregory Haskins <gregory.haskins.ml@xxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: qm@xxxxxxxxx ((null))
• Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: "Ilpo Järvinen" <ilpo.jarvinen@xxxxxxxxxxx>
• RFC: Latency reducing TCP modifications for thin-stream interactive applications
  • From: Andreas Petlund <apetlund@xxxxxxxxx>
• Re: strange getrusage timer problem with rt-kernel
  • From: "Cheng Renquan" <crquan@xxxxxxxxx>
• strange getrusage timer problem with rt-kernel
  • From: crquan@xxxxxxxxx
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: "Alessio Igor Bogani" <abogani@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: "Alessio Igor Bogani" <abogani@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.27.5 RT patch status (26rt11)
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Did anyone tested core i7?
  • From: Amir Aharon <amira@xxxxxxxxx>
• few question about the platform tested and in use with config_preempt_rt...
  • From: Amir Aharon <amira@xxxxxxxxx>
• RE: config_preempt_RT patch platform support question.
  • From: Amir Aharon <amira@xxxxxxxxx>
• RE: config_preempt_RT patch platform support question.
  • From: Amir Aharon <amira@xxxxxxxxx>
• Strange device behavior on SMP system with CONFIG_PREEMPT_RT patch
  • From: "Denis Borisevich" <dennisfen@xxxxxxxxx>
• Re: config_preempt_RT patch platform support question.
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: Network performance forwarding tests on RT
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• config_preempt_RT patch platform support question.
  • From: Amir Aharon <amira@xxxxxxxxx>
• Re: [RFC PATCH 0/3] Series short description
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] Series short description
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] Series short description
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• kernel modules and ftrace
  • From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
• Re: Network performance forwarding tests on RT
  • From: Clark Williams <williams@xxxxxxxxxx>
• 2.6.27.5 RT patch status (26rt11)
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: [PATCH][RT] Dereference pointer to cpu id, not to address of CPUID
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT] Dereference pointer to cpu id, not to address of CPUID
  • From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
• aufs: built it on RT
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• unionfs on RT
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• [PATCH][RT] Trivial: Correctly dereference when clearing unused variable
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Network performance forwarding tests on RT
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH][RT] Dereference pointer to cpu id, not to address of CPUID
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.26.6-rt11 nanosleep() does have accurate behavior
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: Network performance forwarding tests on RT
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• 2.6.26.6-rt11 nanosleep() does have accurate behavior
  • From: Gautam Thaker <gautam.h.thaker@xxxxxxxx>
• Re: Network performance forwarding tests on RT
  • From: Clark Williams <williams@xxxxxxxxxx>
• Network performance forwarding tests on RT
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• Re: nohz=off
  • From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
• Re: nohz=off
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: nohz=off
  • From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
• Re: nohz=off
  • From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
• Re: nohz=off
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: nohz=off
  • From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
• Re: nohz=off
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• nohz=off
  • From: Sergio Monteiro Basto <sergio@xxxxxxxxxxxxxxxxxx>
• Trouble compiling 2.6.26.6-rt11 for ARM
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: [LTP] New LTP test feature [Hard Real Time Linux Testing]
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• Re: [LTP] New LTP test feature [Hard Real Time Linux Testing]
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• rt-tests version 0.28 available
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [PATCH 2/2] netrate - network rate/rtt measurement utility
  • From: Clark Williams <williams@xxxxxxxxxx>
• [PATCH 2/2] netrate - network rate/rtt measurement utility
  • From: Clark Williams <clark.williams@xxxxxxxxx>
• [PATCH 0/2] netrate - network rate/rtt measurement utility
  • From: Clark Williams <clark.williams@xxxxxxxxx>
• [PATCH] Cyclictest Hiistogram Support
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC patch] genirq threading (v2) for ehci, ohci and uhci USB hosts and ohci1394
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC patch] genirq threading for ehci, ohci and uhci USB hosts
  • From: Jonathan Woithe <jwoithe@xxxxxxxxxxxxxxxxxxxxxxx>
• [RFC patch] genirq threading for ehci, ohci and uhci USB hosts
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• [-rt] 2.6.26.6-rt11: Another sleeping function called from invalid context
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• [PATCH -rt] sched: remove unneeded #if directive
  • From: Hiroshi Shimamoto <h-shimamoto@xxxxxxxxxxxxx>
• Re: 2.6.26.6-rt11 boot failure on PREEMPT_DESKTOP
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• 2.6.26.6-rt11 boot failure on PREEMPT_DESKTOP
  • From: Hiroshi Shimamoto <h-shimamoto@xxxxxxxxxxxxx>
• Re: 2.6.26.6-rt10
  • From: Luis Henriques <henrix@xxxxxxx>
• New rt-tests maintainer
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.26.6-rt10
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 2/2] add function_trace_stop
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 1/2] cyclictest: preopen trace_enabled
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.6-rt10
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.6-rt10
  • From: Luis Henriques <henrix@xxxxxxx>
• 2.6.26.6-rt10
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• 2.6.24.7-rt21
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: PF_HARDIRQ used in preempt-realtime-core.patch
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RT PATCH v3 0/2] Fix for "[BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang"
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• Re: PF_HARDIRQ used in preempt-realtime-core.patch
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: PF_HARDIRQ used in preempt-realtime-core.patch
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: PF_HARDIRQ used in preempt-realtime-core.patch
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• PF_HARDIRQ used in preempt-realtime-core.patch
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• [RT PATCH v3 1/2] RT: Remove comment that is no longer true
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v3 2/2] RT: fix push_rt_task() to handle dequeue_pushable properly
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v3 0/2] Fix for "[BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang"
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• 2.6.27-rc8 RT patch status
  • From: "Paul Gortmaker" <paul.gortmaker@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] RT: remove "paranoid" limit in push_rt_task
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v2 2/2] RT: remove "paranoid" limit in push_rt_task
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v2 1/2] RT: Remove comment that is no longer true
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v2 0/2] Series short description
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/2] RT: remove "paranoid" limit in push_rt_task
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] RT: remove "paranoid" limit in push_rt_task
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• Re: [RT PATCH 0/2] fix for BUG_ON crash in 26.5-rt9
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH replace] Fix pushable_tasks list corruption
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 2/2] RT: remove "paranoid" limit in push_rt_task
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH 0/2] fix for BUG_ON crash in 26.5-rt9
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 1/2] RT: Remove comment that is no longer true
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH replace] Fix pushable_tasks list corruption
  • From: Gilles Carry <gilles.carry@xxxxxxxx>
• Re: [PATCH][RT] Fix pushable_tasks list corruption
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• Re: [PATCH][RT] Fix pushable_tasks list corruption
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• [PATCH][RT] Fix pushable_tasks list corruption
  • From: Gilles Carry <gilles.carry@xxxxxxxx>
• Re: [PATCH] sched: add a stacktrace on enqueue_pushable error
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• [PATCH/RFC] init_hardirqs shouldn't call start_irq_thread
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• [PATCH] sched: add a stacktrace on enqueue_pushable error
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• RT points of interest associated with 2.6.27-rcN
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: RT patches against v2.6.27-rc7 available
  • From: "Paul Gortmaker" <paul.gortmaker@xxxxxxxxx>
• Re: RT patches against v2.6.27-rc7 available
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: RT patches against v2.6.27-rc7 available
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• RT patches against v2.6.27-rc7 available
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 3/3] rt: sysctl compile fix for when profiling is off
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• [PATCH 0/3] Compile fixes for disabled config opts.
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• [PATCH 2/3] rt bit spinlocks: fix compile failure for !CONFIG_PREEMPT_RT
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• [PATCH 1/3] compat_rwsem: fix compile failure for when PREEMPT_RT is disabled.
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: [PATCH]Real-time kernel compile-fix for 32-bit when disabling CONFIG_PREEMPT_RT
  • From: "Paul Gortmaker" <paul.gortmaker@xxxxxxxxx>
• [PATCH]Real-time kernel compile-fix for 32-bit when disabling CONFIG_PREEMPT_RT
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26-rt9 Hang
  • From: "David L. Craig" <dlc@xxxxxxxxx>
• 2.6.26-rt9 Hang
  • From: "David L. Craig" <dlc@xxxxxxxxx>
• Re: [PATCH][RT]: handle_IRQ_event() - fix thinko
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [BUG][PPC64] BUG in 2.6.26.5-rt9 causing Hang
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT]: handle_IRQ_event() - fix thinko
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• patch 2.6.26.5 rt9 for ppc
  • From: "dalampu@xxxxxx" <dalampu@xxxxxx>
• Re: [PATCH][RT]: handle_IRQ_event() - fix thinko
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption, eHCA is close
  • From: Jan-Bernd Themann <ossthema@xxxxxxxxxx>
• [PATCH][RT]: handle_IRQ_event() - fix thinko
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• 2.6.26.5-rt9 without PREEMPT RT gives undefined reference to `kernel_sem'
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption, eHCA is close
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption, eHCA is close
  • From: Christoph Raisch <RAISCH@xxxxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Christoph Raisch <RAISCH@xxxxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Anton Vorontsov <avorontsov@xxxxxxxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Thomas Klein <osstklei@xxxxxxxxxx>
• [PATCH HACK] powerpc: quick hack to get a functional eHEA with hardirq preemption
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• 2.6.24.7-rt20
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.5-rt9
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.5-rt9
  • From: Robert Schwebel <robert@xxxxxxxxxxx>
• [PATCH 2.6.26.5-rt9] remove duplicate save_stack_trace
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• 2.6.26.5-rt9
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• 2.6.24.7-rt19
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RT] tasklets: fix __tasklet_hi_schedule()
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH RT] tasklets: fix __tasklet_hi_schedule()
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• mpc5200: 2.6.3-rt7: Timer subsystem WARN_ON_ONCE causing large latencies
  • From: "Pradyumna Sampath" <pradysam@xxxxxxxxx>
• [PATCH] duplicate zap_rt_locks in preempt-realtime-core.patch
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt18
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.5-rt8
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.5-rt8
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.24.7-rt18
  • From: Ankita Garg <ankita@xxxxxxxxxx>
• 2.6.26.5-rt8
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• 2.6.24.7-rt18
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.3 with rt3 patch: BUG: sleeping function called kernel/rtmutex.c:743
  • From: "xavier droubay" <xavier.droubay@xxxxxxxxx>
• Re: [PATCH] Convert tlbstate_lock spin_lock to raw_spin_lock
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: "Karthik Singaram Lakshmanan" <karthiksingaram@xxxxxxxxx>
• Re: [PATCH] Convert tlbstate_lock spin_lock to raw_spin_lock
  • From: "Sujit Karataparambil" <sjt.kar@xxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• [PATCH] Convert tlbstate_lock spin_lock to raw_spin_lock
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• 2.6.26.3 with rt3 patch: BUG: sleeping function called kernel/rtmutex.c:743
  • From: "xavier droubay" <xavier.droubay@xxxxxxxxx>
• 2.6.26.3-rt7
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Re: Question regarding sched_setaffinity
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• 2.6.26.3-rt6
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [TIP/SCHED/DEVEL PATCH v3 6/6] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: [TIP/SCHED/DEVEL PATCH v3 6/6] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [TIP/SCHED/DEVEL PATCH v3 4/6] sched: add sched_class->needs_post_schedule() member
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: [TIP/SCHED/DEVEL PATCH v3 4/6] sched: add sched_class->needs_post_schedule() member
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 6/6] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 5/6] plist: fix PLIST_NODE_INIT to work with debug enabled
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 4/6] sched: add sched_class->needs_post_schedule() member
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 2/6] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 0/6] sched: misc rt fixes
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [TIP/SCHED/DEVEL PATCH v3 1/6] sched: only try to push a task on wakeup if it is migratable
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 1/2] powerpc - Separate the irq radix tree insertion and lookup
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 0/2 V4] powerpc - Make the irq reverse mapping tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• 2.6.26.3-rt5
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 1/2] powerpc - Separate the irq radix tree insertion and lookup
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• 2.6.26.3-rt4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [RT PATCH v4] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RT PATCH v3] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [RT PATCH v3] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Question regarding sched_setaffinity
  • From: "Karthik Singaram Lakshmanan" <karthiksingaram@xxxxxxxxx>
• Re: 2.6.26.3-rt3 bug report
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: [RT PATCH v2] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RT PATCH v2] seqlock: serialize against writers
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RT PATCH v2] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [RT PATCH v2] seqlock: serialize against writers
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RT PATCH v2] seqlock: serialize against writers
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• [RT PATCH v2] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [ RT PATCH] seqlock: serialize against writers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: [PATCH] seqlock: serialize against writers
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• [PATCH] seqlock: serialize against writers
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.3-rt3 bug report
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH v2 6/6] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: Availability rt patch for older linux kernel 2.6.11.3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Nick Piggin <npiggin@xxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Nick Piggin <npiggin@xxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Nick Piggin <npiggin@xxxxxxx>
• Re: [PATCH v2 0/6] Series short description
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH v2 0/6] sched: misc rt fixes for tip/sched/devel (was: Series short description)
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• [PATCH v2 6/6] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 5/6] plist: fix PLIST_NODE_INIT to work with debug enabled
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 4/6] sched: add sched_class->needs_post_schedule() member
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 3/6] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 2/6] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 0/6] Series short description
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH v2 1/6] sched: only try to push a task on wakeup if it is migratable
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH] Subject: x86: Move crashkernel reservation before dma32_reserve_bootmem()
  • From: Bernhard Walle <bwalle@xxxxxxx>
• Re: [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 3/5] sched: make double-lock-balance fair
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: 2.6.26.3-rt3 bug report
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: 2.6.26.3-rt3 bug report
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Re: 2.6.26.3-rt3 bug report
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• [PATCH 5/5] sched: create "pushable_tasks" list to limit pushing to one attempt
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 4/5] sched: add sched_class->needs_post_schedule() member
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 3/5] sched: make double-lock-balance fair
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 1/5] sched: only try to push a task on wakeup if it is migratable
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 0/5] sched: misc rt fixes for tip/sched/devel
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Gilles Carry <Gilles.Carry@xxxxxxxx>
• [PATCH] Subject: x86: Move crashkernel reservation before dma32_reserve_bootmem()
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Availability rt patch for older linux kernel 2.6.11.3
  • From: robert <robje99@xxxxxxxxxxx>
• 2.6.26.3-rt3 bug report
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26.3-rt3
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26.3-rt3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.3-rt3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.3-rt3
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• 2.6.26.3-rt3
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: "Esben Nielsen" <nielsen.esben@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] [RT] hrtimer __run_hrtimer code cleanup
  • From: Gilles Carry <glscarry@xxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Gilles Carry <glscarry@xxxxxxx>
• Re: 2.6.26.3-rt2
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26.3-rt2
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26.3-rt2
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.26.3-rt2
  • From: "Javier Sanz" <jsanza@xxxxxxxxx>
• 2.6.26.3-rt2
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH 2/2] [RT] hrtimer __run_hrtimer code cleanup
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Motherboard chipset advise needed.
  • From: "Denis Borisevich" <dennisfen@xxxxxxxxx>
• Re: [PATCH 2/2] [RT] hrtimer __run_hrtimer code cleanup
  • From: Gilles Carry <glscarry@xxxxxxx>
• Re: [PATCH 2/2] [RT] hrtimer __run_hrtimer code cleanup
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: [PATCH] rt Kconfig.preempt fixes
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH] rt Kconfig.preempt fixes
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] powerpc - Separate the irq radix tree insertion and lookup
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Patches to drop from the next RT series
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Review comments/questions on preempt-irqs-i386.patch
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RT 2/2] ftrace: fix elevated preempt_count in wakeup-tracer
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH RT 2/2] ftrace: fix elevated preempt_count in wakeup-tracer
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH RT 2/2] ftrace: fix elevated preempt_count in wakeup-tracer
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RT 2/2] ftrace: fix elevated preempt_count in wakeup-tracer
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH RT 2/2] ftrace: fix elevated preempt_count in wakeup-tracer
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT 1/2] seqlock: make sure that raw_seqlock_t retries readers while writes are pending
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT 0/2] Misc fixes for 2.6.26-rt1
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: AW: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 1/2] [RT] hrtimers stuck in waitqueue
  • From: Gilles Carry <gilles.carry@xxxxxxxx>
• [PATCH 2/2] [RT] hrtimer __run_hrtimer code cleanup
  • From: Gilles Carry <gilles.carry@xxxxxxxx>
• [PATCH 0/2][RT] hrtimers stuck in waitqueue
  • From: Gilles Carry <gilles.carry@xxxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• AW: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: "Matthias Behr" <linux@xxxxxxxxx>
• ARM RT - "scheduling with irqs disabled" can occur when a break point is set
  • From: Jim Barlow <jbarlow@xxxxxxx>
• Re: [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• [PATCH RT RFC v4 8/8] rtmutex: pi-boost locks as late as possible
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 7/8] rtmutex: convert rtmutexes to fully use the PI library
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 6/8] rtmutex: use runtime init for rtmutexes
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 5/8] RT: wrap the rt_rwlock "add reader" logic
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 4/8] rtmutex: formally initialize the rt_mutex_waiters
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 3/8] sched: rework task reference counting to work with the pi infrastructure
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 2/8] sched: add the basic PI infrastructure to the task_struct
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v4 0/8] Priority Inheritance enhancements
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH] Compile problems in locking-selftest.c with CONFIG_DEBUG_PREEMPT
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• [PATCH RT] fix flags in usb code
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH RT] infiniband: change flags from int to long
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH RT RFC v3] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 6/8] rtmutex: use runtime init for rtmutexes
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 0/8] Priority Inheritance enhancements
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 5/8] RT: wrap the rt_rwlock "add reader" logic
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 3/8] sched: rework task reference counting to work with the pi infrastructure
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 2/8] sched: add the basic PI infrastructure to the task_struct
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 8/8] rtmutex: pi-boost locks as late as possible
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 7/8] rtmutex: convert rtmutexes to fully use the PI library
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 1/8] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC v2 4/8] rtmutex: formally initialize the rt_mutex_waiters
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• [PATCH] rt: shorten posix_cpu_timers/<CPU> kernel thread names
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: 2.6.26-rt1
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.26-rt1
  • From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• 2.6.26-rt1 : trying to register non-static key.
  • From: Sripathi Kodi <sripathik@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• LPPTEST-worst-case latency
  • From: Kushal Koolwal <kushalkoolwal@xxxxxxxxxxx>
• Re: [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: David Miller <davem@xxxxxxxxxxxxx>
• LPPTEST-worst-case latency
  • From: Kushal Koolwal <kushalkoolwal@xxxxxxxxxxx>
• Re: Cyclictest usage
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• [PATCH] BUG: using smp_processor_id() in preemptible [00000000] code: caller is __qdisc_run
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: Cyclictest usage
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Cyclictest usage
  • From: "Tobias Knutsson" <tobias.knutsson@xxxxxxxxx>
• Re: 2.6.26-rt1
  • From: Juergen Beisert <jbe@xxxxxxxxxxxxxx>
• [PATCH] Fix typo in pi_stress manpage
  • From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
• [PATCH] Avoid to remove too much files
  • From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
• [PATCH][PPC64][RT] Fix a previously reverted fix again
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Preempt-RT with Linux 2.6.20 for Arch ppc
  • From: "Christian Volk" <linux.kernel@xxxxxxxx>
• [PATCH 2/2] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 1/2] powerpc - Separate the irq radix tree insertion and lookup
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 0/2 V3] powerpc - Make the irq reverse mapping tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• tracing WARN_ON in rt kernel
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Newbie: LPPTEST script question
  • From: Kushal Koolwal <kushalkoolwal@xxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: mark gross <mgross@xxxxxxxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: [PATCH 3/3] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 1/3] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH RFC] pm_qos_requirement might sleep
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH RT RFC 7/7] rtmutex: pi-boost locks as late as possible
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: 2.6.25.8-rt7 Bugs
  • From: "Mark Knecht" <markknecht@xxxxxxxxx>
• Re: [PATCH 1/3] powerpc - Initialize the irq radix tree earlier
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] powerpc - Initialize the irq radix tree earlier
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• [PATCH RFC] pm_qos_requirement might sleep
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH 3/3] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Daniel Walker <dwalker@xxxxxxxxxx>
• [PATCH 3/3] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 2/3] powerpc - Separate the irq radix tree insertion and lookup
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 1/3] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 0/3 V2] powerpc - Make the irq reverse mapping tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH RT RFC 7/7] rtmutex: pi-boost locks as late as possible
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: 2.6.25.8-rt7 Bugs
  • From: Matthew Smith <matt@xxxxxxxxxxxxxx>
• Re: Can't boot 2.6.26-rt1
  • From: "Justin Mattock" <justinmattock@xxxxxxxxx>
• Re: Can't boot 2.6.26-rt1
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: Can't boot 2.6.26-rt1
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Can't boot 2.6.26-rt1
  • From: "Justin Mattock" <justinmattock@xxxxxxxxx>
• Can't boot 2.6.26-rt1
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: newbie, rt programming and concepts books, training
  • From: Alejandro Mery <amery@xxxxxxxxxxx>
• newbie, rt programming and concepts books, training
  • From: "Javier Sanz" <jsanza@xxxxxxxxx>
• [PATCH RT RFC 7/7] rtmutex: pi-boost locks as late as possible
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 6/7] rtmutex: convert rtmutexes to fully use the PI library
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 5/7] rtmutex: use runtime init for rtmutexes
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 4/7] RT: wrap the rt_rwlock "add reader" logic
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 3/7] rtmutex: formally initialize the rt_mutex_waiters
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 2/7] sched: add the basic PI infrastructure to the task_struct
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 1/7] add generalized priority-inheritance interface
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH RT RFC 0/7] Priority Inheritance enhancements
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH -rt] apply rcu_process_callbacks() changes from mainline
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.26-rt1
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.26-rt1
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• 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: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• [PATCH] rt Kconfig.preempt fixes
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.25.8-rt7 Bugs
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• 2.6.25.8-rt7 Bugs
  • From: Matthew Smith <matt@xxxxxxxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH 0/3] powerpc - Make the irq reverse mapping tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 0/3] powerpc - Make the irq reverse mapping tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH] powerpc - Initialize the irq radix tree earlier
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH] powerpc - Separate the irq radix tree insertion and lookup
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH] Fix Bug messages
  • From: Jürgen Mell <j.mell@xxxxxxxxxxx>
• [PATCH] Fix Bug messages
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.26-rt1
  • From: "Ryan Hope" <rmh3093@xxxxxxxxx>
• Re: 2.6.26-rt1
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: 2.6.26-rt1
  • From: Jürgen Mell <j.mell@xxxxxxxxxxx>
• 2.6.26-rt1
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: PCI: MSI interrupts masked using prohibited method
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Re: Questions About preempt-rt and arch:ppc
  • From: "Christian Volk" <linux.kernel@xxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: PCI: MSI interrupts masked using prohibited method
  • From: Michal Schmidt <mschmidt@xxxxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt16
  • From: "Avuton Olrich" <avuton@xxxxxxxxx>
• Re: Questions About preempt-rt and arch:ppc
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• 2.6.24.7-rt16
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt15
  • From: Jaswinder Singh <jaswinder@xxxxxxxxxxxxx>
• Re: 2.6.24.7-rt15
  • From: Daniel Walker <dwalker@xxxxxxxxxx>
• Re: 2.6.24.7-rt15
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: 2.6.24.7-rt15
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.24.7-rt15
  • From: Jaswinder Singh <jaswinder@xxxxxxxxxxxxx>
• 2.6.24.7-rt15
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 0/2][RT] powerpc - fix bug in irq reverse mapping radix tree
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 2/2][RT] powerpc - Make the irq reverse mapping radix tree lockless
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 1/2][RT] powerpc - XICS: move the call to irq_radix_revmap from xics_startup to xics_host_map
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH 0/2][RT] powerpc - fix bug in irq reverse mapping radix tree (Resend)
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH 0/2][RT] powerpc - fix bug in irq reverse mapping radix tree
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] sched: remove extraneous load manipulations
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Questions About preempt-rt and arch:ppc
  • From: "Christian Volk" <linux.kernel@xxxxxxxx>
• Re: [PATCH 2/2] sched: readjust the load whenever task_setprio()is invoked
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH 1/2] sched: remove extraneous load manipulations
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/2] sched: readjust the load whenever task_setprio() is invoked
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] sched: remove extraneous load manipulations
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• [PATCH] Fix typo in pi_stress manpage
  • From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
• [PATCH] Differentiate hyphen and minus in manpages
  • From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
• Re: rt for 2.6.26?
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• Re: 2.6.25.X-rtX compile errors on ARM due to cmpxchg() problems.
  • From: "Remy Bohmer" <linux@xxxxxxxxxx>
• Re: rt for 2.6.26?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• rt for 2.6.26?
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• [PATCH RT] rwlock: be more conservative in locking reader_lock_count
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: Real time linux on my project
  • From: Henrik Austad <henrikau@xxxxxxxxxxxxxx>
• Re: Real time linux on my project
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Real time linux on my project
  • From: Luis <lquirosr@xxxxxxxxx>
• Re: [PATCH] ftrace: Actually call function pointer in ftrace_stop
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] ftrace: Actually call function pointer in ftrace_stop
  • From: Josh Triplett <josht@xxxxxxxxxxxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• Re: [PATCH][RT][PPC64] Fix a previously reverted "fix"
  • From: Sebastien Dugue <sebastien.dugue@xxxxxxxx>
• [PATCH][RT][PPC64] Fix a previously reverted "fix"
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: [PATCH 2.6.24.7-rt14 v2] rt: {queue,schedule}_work_prio() allowing work priorities other than caller's priority
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables
  • From: Chirag Jog <chirag@xxxxxxxxxxxxxxxxxx>
• 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: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: add mlockall option to cyclictest, et al
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] sched: newidle and RT wake-buddy fixes
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Luotao Fu <l.fu@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] sched: newidle and RT wake-buddy fixes
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: add mlockall option to cyclictest, et al
  • From: Daniel Gollub <dgollub@xxxxxxx>
• Re: [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• Re: [PATCH] Fix the processing of optional options for cyclictest
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH][resubmit] x86: enable preemption in delay
  • From: Pavel Machek <pavel@xxxxxxx>
• 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: Wolfgang Grandegger <wg@xxxxxxxxxxxxxx>
• ARM PXA255 build error and hundreds warnings
  • From: GSE <guillaume.sempe@xxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: 2.6.24-rc8-rt1: Strange latencies on mpc5200 powerpc - RCU issue?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [PATCH -rt] [resend as inlined patch] {queue,schedule}_work_prio() allowing work priorities other than caller's priority
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• [PATCH 2.6.24.7-rt14 v2] rt: {queue,schedule}_work_prio() allowing work priorities other than caller's priority
  • From: leon.woestenberg@xxxxxxxxx
• [test - ignore] kernel patch submission script using msmtp/gmail
  • From: leon.woestenberg@xxxxxxxxx
• [test - ignore] kernel patch submission script using msmtp/gmail
  • From: leon.woestenberg@xxxxxxxxx
• Re: [PATCH -rt] [resend as inlined patch] {queue,schedule}_work_prio() allowing work priorities other than caller's priority
  • From: Daniel Walker <dwalker@xxxxxxxxxx>
• [PATCH -rt] [resend as inlined patch] {queue,schedule}_work_prio() allowing work priorities other than caller's priority
  • From: Leon Woestenberg <leon.woestenberg@xxxxxxxxx>
• Re: [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: "John Kacur" <jkacur@xxxxxxxxx>
• [RFC][PATCH] fix SCHED_FIFO spec violation (backport)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH 2/2] sched: readjust the load whenever task_setprio() is invoked
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• [PATCH 1/2] sched: remove extraneous load manipulations
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>