Linux Real Time Users

• Thread Index

• Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: Jon Masters <jcm@xxxxxxxxxx>
• Using -rt and TuxOnIce at the same time
  • From: Pedro Ribeiro <pedrib@xxxxxxxxx>
• Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: -rt kernel hitting yield()s in I2C non-default code paths (2.6.24)
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Odd bug in SATA link power management
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: nvidia-kernel-source 185.18.36-2 fails to build against linux-image-2.6.31.2-rt13-1-amd64
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• -rt kernel hitting yield()s in I2C non-default code paths (2.6.24)
  • From: Leon Woestenberg <leon.woestenberg@xxxxxxxxx>
• Re: Odd bug in SATA link power management
  • From: Lee Revell <rlrevell@xxxxxxxxxxx>
• Odd bug in SATA link power management
  • From: Pedro Ribeiro <pedrib@xxxxxxxxx>
• Re: [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: A question about cpu_idle()
  • From: yi li <liyi.dev@xxxxxxxxx>
• Re: [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [patch -rt] Fix infinite loop with 2.6.31.4-rt14 V2
  • From: Dinakar Guniguntala <dino@xxxxxxxxxx>
• Re: [patch -rt] Fix infinite loop with 2.6.31.4-rt14
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [patch -rt] Fix infinite loop with 2.6.31.4-rt14
  • From: Dinakar Guniguntala <dino@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org (v2)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org (v2)
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH -rt] Updates-from-Jon-Masters-for-hwlat_detector.c.patch
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org (v2)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• proposed FAQ entry for rt.wiki.kernel.org (v3)
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org (v2)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• proposed FAQ entry for rt.wiki.kernel.org (v2)
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: A question about cpu_idle()
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposed FAQ entry for rt.wiki.kernel.org
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• proposed FAQ entry for rt.wiki.kernel.org
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: A question about cpu_idle()
  • From: yi li <liyi.dev@xxxxxxxxx>
• [patch -rt 07/17] sched: try to deal with low capacity
  • From: dino@xxxxxxxxxx
• [patch -rt 05/17] sched: dynamic cpu_power
  • From: dino@xxxxxxxxxx
• [patch -rt 14/17] sched: cleanup wake_idle
  • From: dino@xxxxxxxxxx
• [patch -rt 11/17] Provide an arch specific hook for cpufreq based scaling of cpu_power.
  • From: dino@xxxxxxxxxx
• [patch -rt 13/17] sched: cleanup wake_idle power saving
  • From: dino@xxxxxxxxxx
• [patch -rt 09/17] x86: move APERF/MPERF into a X86_FEATURE
  • From: dino@xxxxxxxxxx
• [patch -rt 17/17] sched: Fix dynamic power-balancing crash
  • From: dino@xxxxxxxxxx
• [patch -rt 03/17] sched: update the cpu_power sum during load-balance
  • From: dino@xxxxxxxxxx
• [patch -rt 08/17] sched: remove reciprocal for cpu_power
  • From: dino@xxxxxxxxxx
• [patch -rt 00/17] [patch -rt] Sched load balance backport
  • From: dino@xxxxxxxxxx
• [patch -rt 04/17] sched: add smt_gain
  • From: dino@xxxxxxxxxx
• [patch -rt 12/17] x86: sched: provide arch implementations using aperf/mperf
  • From: dino@xxxxxxxxxx
• [patch -rt 16/17] sched: Deal with low-load in wake_affine()
  • From: dino@xxxxxxxxxx
• [patch -rt 06/17] sched: scale down cpu_power due to RT tasks
  • From: dino@xxxxxxxxxx
• [patch -rt 10/17] x86: Add generic aperf/mperf code
  • From: dino@xxxxxxxxxx
• [patch -rt 15/17] sched: Add a missing =
  • From: dino@xxxxxxxxxx
• [patch -rt 02/17] sched: SD_PREFER_SIBLING
  • From: dino@xxxxxxxxxx
• [patch -rt 01/17] sched: restore __cpu_power to a straight sum of power
  • From: dino@xxxxxxxxxx
• Re: A question about cpu_idle()
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• Re: MIPS port
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• MIPS port
  • From: fabio <fabio7774@xxxxxxxxx>
• Re: A question about cpu_idle()
  • From: yi li <liyi.dev@xxxxxxxxx>
• Re: A question about cpu_idle()
  • From: "Gregory Haskins" <ghaskins@xxxxxxxxxx>
• A question about cpu_idle()
  • From: yi li <liyi.dev@xxxxxxxxx>
• Re: [PATCH] futex: Detect mismatched requeue targets
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [PATCH] futex: Detect mismatched requeue targets
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH -tip] rt: Fix the follow oops
  • From: Alessio Igor Bogani <abogani@xxxxxxxxxx>
• [PATCH RT] Consider shared max priority in latency histograms
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: [PATCH] futex: Detect mismatched requeue targets
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH -rt] Futex Comments-fix-ups (from Darren Hart)
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Fwd: MIPS SUPPORT with rt-24
  • From: John Kacur <jkacur@xxxxxxxxx>
• [PATCH] futex: Detect mismatched requeue targets
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: MIPS SUPPORT with rt-24
  • From: John Kacur <jkacur@xxxxxxxxx>
• MIPS SUPPORT with rt-24
  • From: fabio <fabio7774@xxxxxxxxx>
• Re: fork() blocking rt-threads?
  • From: Lee Revell <rlrevell@xxxxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: fabio <fabio7774@xxxxxxxxx>
• Re: fork() blocking rt-threads?
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: fork() blocking rt-threads?
  • From: Lee Revell <rlrevell@xxxxxxxxxxx>
• possible bug in cyclictest
  • From: Bernhard Schiffner <bernhard@xxxxxxxxxxxxxxxxxxxx>
• Re: fork() blocking rt-threads?
  • From: Nedko Arnaudov <nedko@xxxxxxxxxxxxx>
• Re: fork() blocking rt-threads?
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• fork() blocking rt-threads?
  • From: <hollunder@xxxxxx>
• [Fwd: Re: 2.6.31.4-rt14 posix message queues problem (solved)]
  • From: Joerg Abraham <Joerg.Abraham@xxxxxxxxxxxxxxxxx>
• Re: 2.6.31.4-rt14 posix message queues problem
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [ANNOUNCE] 2.6.31.4-rt14
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: Bug in timekeeping.c ktime_get_ts() Kernel 2.2.29.6-rt23
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Simplify the code in cpuid_open
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC] BKL not necessary in cpuid_open
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• [PATCH RFC] BKL not necessary in cpuid_open
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: Using set_irq_handler in set_irq_type callback?
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Using set_irq_handler in set_irq_type callback?
  • From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
• Re: Using set_irq_handler in set_irq_type callback?
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Using set_irq_handler in set_irq_type callback?
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] time: remove xtime_cache
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH 1/2] time: logrithmic time accumulation
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31.2-rt13
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• [ANNOUNCE] 2.6.31.2-rt13
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Hans-Peter Bock <Hans-Peter.Bock@xxxxxxxxxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Re: [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Frederik Deweerdt <frederik.deweerdt@xxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Hans-Peter Bock <Hans-Peter.Bock@xxxxxxxxxxxxxxxxxxxx>
• Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Problem with network on kernel 2.6.29.6-rt23 (Debian)
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Azraiyl <azraiyl@xxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Please advice on realtime application architecture
  • From: "Nikita V. Youshchenko" <yoush@xxxxxxxxx>
• Re: Problems with FTrace
  • From: gowrishankar <gowrishankar.m@xxxxxxxxxxxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: slab_irq_enable is receiving corrupted / deleted list entries
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• is there a PREEMPT-realtime patch for stable kernel version 2.6.31.1 ??
  • From: Gautam Thaker <gautam.h.thaker@xxxxxxxx>
• Re: [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• Re: [ANNOUNCE] Linux-RT for Debian
  • From: Jose Angel Martinez Conde <joseangel@xxxxxxxxxxxxx>
• Re: realtime kernel for Debian
  • From: rosea grammostola <rosea.grammostola@xxxxxxxxx>
• Re: realtime kernel for Debian
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• slab_irq_enable is receiving corrupted / deleted list entries
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Oliver Neukum <oliver@xxxxxxxxxx>
• Re: [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Frederik Deweerdt <frederik.deweerdt@xxxxxxxx>
• [PATCH][UHCI-DEBUG] Don't kmalloc with BKL held
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: Problem with 2.6.31-rt11 + iptables on shutdown
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: Problem with 2.6.31-rt11 + iptables on shutdown
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with 2.6.31-rt11 + iptables on shutdown
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Problem with 2.6.31-rt11 + iptables on shutdown
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Azraiyl <azraiyl@xxxxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Azraiyl <azraiyl@xxxxxxxxx>
• Problems with FTrace
  • From: Paolo <prallo@xxxxxxxxx>
• Re: [archival] 2.6.31-rt nvidia patches
  • From: Ng Oon-Ee <ngoonee@xxxxxxxxx>
• Re: R:[ANNOUNCE] Linux-RT for Debian
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH] get rid of [softirq-NULL]
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: RT Latency on Atmel Processors
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: [PATCH] get rid of [softirq-NULL]
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• [PATCH] get rid of [softirq-NULL]
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Jan Blunck <jblunck@xxxxxxx>
• RT Latency on Atmel Processors
  • From: Azraiyl <azraiyl@xxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: yi li <liyi.dev@xxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: 2.6.31-rt11 freeze on userland start on ARM
  • From: Azraiyl <azraiyl@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• 2.6.31-rt11 freeze on userland start on ARM
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Sujit K M <sjt.kar@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Sujit K M <sjt.kar@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Jaswinder Singh Rajput <jaswinder@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt11
  • From: Jaswinder Singh Rajput <jaswinder@xxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rt11
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: xjadeo
  • From: Georg Mill <info@xxxxxxxxxxxx>
• Re: xjadeo
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• 2.6.31-rt10 crash
  • From: John Kacur <jkacur@xxxxxxxxx>
• xjadeo
  • From: Georg Mill <info@xxxxxxxxxxxx>
• SoftIRQ preemption
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rt10
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rt10
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [SOLVED, RFC] Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 3/3] A few more miscellaneous clean-ups.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 2/3] Convert C99 commenting style to C89 style
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 1/3] Run cleanpatch on pi_stress.c
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH 6/6] pi_stress clean-ups, fix hang.
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH] A few more miscellaneous clean-ups.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH RT] Add histograms of potential and effective wakeup latencies
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH RT] Add histograms of potential and effective wakeup latencies
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• [PATCH] Convert C99 commenting style to C89 style, like in the linux kernel.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH] Run cleanpatch on pi_stress.c
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 6/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 6/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 5/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 4/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 3/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 2/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [PATCH 1/6] pi_stress clean-ups, fix hang.
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• [archive] 2.6.31-rt timekeeping workaround
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• [archival] 2.6.31-rt nvidia patches
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with function select on kernel 2.6.29.6-rt23
  • From: Sujit K M <sjt.kar@xxxxxxxxx>
• Problem with function select on kernel 2.6.29.6-rt23
  • From: Jürgen Mell <mell@xxxxxxxxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: IRQ timeout
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: IRQ timeout
  • From: Hans-Peter Bock <Hans-Peter.Bock@xxxxxxxxxxxxxxxxxxxx>
• Re: IRQ timeout
  • From: John Ogness <john.ogness@xxxxxxxxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: IRQ timeout
  • From: Hans-Peter Bock <Hans-Peter.Bock@xxxxxxxxxxxxxxxxxxxx>
• Re: IRQ timeout
  • From: John Ogness <john.ogness@xxxxxxxxxxxxx>
• IRQ timeout
  • From: Hans-Peter Bock <Hans-Peter.Bock@xxxxxxxxxxxxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc9-rt9.1
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH 2/2] fec: don't enable irqs in hard irq context
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: [PATCH 00/18] tracing/ring-buffer: fixes for latency tracer [2.6.32]
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Patch to add the TimerFD API to "cyclictest"
  • From: OB <obconseil@xxxxxxxxx>
• [PATCH] [RT] fix the non-RT version of swap_get_cpu_var
  • From: Wu Zhangjin <wuzhangjin@xxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Cliff Brake <cliff.brake@xxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Cliff Brake <cliff.brake@xxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Koen Kooi <k.kooi@xxxxxxxxxxxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] fec: don't enable irqs in hard irq context
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] fec: fix recursive locking of mii_lock
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] fec: fix recursive locking of mii_lock
  • From: Greg Ungerer <gerg@xxxxxxxxxxxx>
• Re: [PATCH 2/2] fec: don't enable irqs in hard irq context
  • From: Greg Ungerer <gerg@xxxxxxxxxxxx>
• Re: RFC: methods of sched event tracing and my assumptions
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc7-rt8
  • From: Wu Zhangjin <wuzhangjin@xxxxxxxxx>
• [PATCH 1/2] fec: fix recursive locking of mii_lock
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 2/2] fec: don't enable irqs in hard irq context
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Cliff Brake <cliff.brake@xxxxxxxxx>
• Re: RT tests on OMAP3
  • From: Cliff Brake <cliff.brake@xxxxxxxxx>
• Re: RFC: methods of sched event tracing and my assumptions
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• RT tests on OMAP3
  • From: Cliff Brake <cliff.brake@xxxxxxxxx>
• [PATCH] Allocate memory before disabling memory in irq_to_desc_alloc_node()
  • From: Jan Blunck <jblunck@xxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• [PATCH] Re: Latest PreemptRT patch error on imx35
  • From: Tim Sander <tim01@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Latest PreemptRT patch error on imx35
  • From: Tim Sander <tim01@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Latest PreemptRT patch error on imx35
  • From: Tim Sander <tim01@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Latest PreemptRT patch error on imx35
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: Latest PreemptRT patch error on imx35
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Latest PreemptRT patch error on imx35
  • From: Tim Sander <tim01@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Process with SCHED_FIFO policy takes more time than SCHED_OTHER policy
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: System lockup with 2.6.26.8-rt16 on ARM9 [Solved]
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: jim owens <jowens@xxxxxx>
• Re: System lockup with 2.6.26.8-rt16 on ARM9 [Solved]
  • From: Daniel Walker <dwalker@xxxxxxxxxx>
• Re: System lockup with 2.6.26.8-rt16 on ARM9 [Solved]
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc7-rt8
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: jim owens <jowens@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc7-rt8
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: fche@xxxxxxxxxx (Frank Ch. Eigler)
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v2] cyclictest: add --update_on_max option
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Ingo Molnar <mingo@xxxxxxx>
• [ANNOUNCE] 2.6.31-rc7-rt8
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• cyclictest: add --update_on_max option
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• RE: RFC: THE OFFLINE SCHEDULER
  • From: Chetan.Loke@xxxxxxxxxx
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Maxim Levitsky <maximlevitsky@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Raz <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Éric Piel <E.A.B.Piel@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: About update-server-info of rt-tests git tree
  • From: GeunSik Lim <leemgs1@xxxxxxxxx>
• mod_timer() with interrupt disabled (RT patch)
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: About update-server-info of rt-tests git tree
  • From: Clark Williams <williams@xxxxxxxxxx>
• might_sleep warnings 'temporary hack'
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• RTLWS11, Spetember 28-30, TU Dresden, Germany - Call for Participation
  • From: Nicholas Mc Guire <mcguire@xxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Vivek Satpute <vivek@xxxxxxxxxxxxxx>
• About update-server-info of rt-tests git tree
  • From: GeunSik Lim <leemgs1@xxxxxxxxx>
• System lockup with 2.6.26.8-rt16 on ARM9
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: Mike Galbraith <efault@xxxxxx>
• Re: RFC: THE OFFLINE SCHEDULER
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt6
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc6-rt6
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt5
  • From: Dinakar Guniguntala <dino@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt5
  • From: john stultz <johnstul@xxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc6-rt5
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• Re[2]: hrtimer problem on AT91RM9200
  • From: "Bo Hansen" <bh@xxxxxxxxx>
• Re: hrtimer problem on AT91RM9200
  • From: Remy Bohmer <linux@xxxxxxxxxx>
• hrtimer problem on AT91RM9200
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: john stultz <johnstul@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: john stultz <johnstul@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: john stultz <johnstul@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc6-rt2
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc6-rt4
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: kernel oops 2.6.31-rc6-rt2
  • From: Bo Hansen <bh@xxxxxxxxx>
• Re: kernel oops 2.6.31-rc6-rt2
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: 2.6.31-rc6-rt3 oops
  • From: John Kacur <jkacur@xxxxxxxxx>
• 2.6.31-rc6-rt3 oops
  • From: John Kacur <jkacur@xxxxxxxxx>
• 2.6.31-rc6-rt2 bug report
  • From: Dale Stimson <DaleStimson@xxxxxxxxx>
• kernel oops 2.6.31-rc6-rt2
  • From: Bo Hansen <bh@xxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc6-rt2
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: [PATCH -rt] Fix kmap_high_get()
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH -rt] Fix kmap_high_get()
  • From: Nicolas Pitre <nico@xxxxxxxxxxx>
• [PATCH -rt] Fix kmap_high_get()
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: New to list, rt-kernel question re Ubuntu 9.04
  • From: Tobias Knutsson <tobias.knutsson@xxxxxxxxx>
• [PATCH] futex: detect mismatched requeue targets
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH] [RFC, RT] fix kmap_high_get
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• New to list, rt-kernel question re Ubuntu 9.04
  • From: "Henry W. Peters" <hwpeters@xxxxxxxxxxxx>
• [Fwd: Re: sdhci can turn off irq up to 200 ms]
  • From: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• Re: [PATCH][RT] pty low latency
  • From: John Kacur <jkacur@xxxxxxxxx>
• Re: [PATCH][RT] Fix build errors in rtmutex
  • From: John Kacur <jkacur@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• [PATCH][RT] btrfs compile fix
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• [PATCH][RT] pty low latency
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• [PATCH][RT] Fix build errors in rtmutex
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• [ANNOUNCE] linux-2.6.31-rc5-rt1.2
  • From: John Kacur <jkacur@xxxxxxxxxx>
• [RT PATCH] Changed boot warning to look for CONFIG_FUNCTION && !CONFIG_DYNAMIC_FTRACE
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: remembering rt-sched attributes - was: [LAD] rtirq script is broken with 2.6.31
  • From: Robin Gareus <robin@xxxxxxxxxx>
• 2.6.29.6-rt23 - Locking API testsuite Fail
  • From: taejin kim <tj7.kim@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• CONFIG_4KSTACK with rt patch
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: remembering rt-sched attributes - was: [LAD] rtirq script is broken with 2.6.31
  • From: Rui Nuno Capela <rncbc@xxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with hwlat detector in smp_processor_id()
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH V2] futex: Fix handling of bad requeue syscall pairing
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 5/6] [NET] ixp2000/enp2611: don't set non-existent member get_stats
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: Problem with hwlat detector in smp_processor_id()
  • From: Wolfgang Steinwender <wolfgang@xxxxxxxxxxx>
• [PATCH] futex: fix compat_futex to be same as futex for REQUEUE_PI
  • From: Dinakar Guniguntala <dino@xxxxxxxxxx>
• Re: [PATCH 5/6] [NET] ixp2000/enp2611: don't set non-existent member get_stats
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 5/6] [NET] ixp2000/enp2611: don't set non-existent member get_stats
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH RT v3] futex: update futex_q lock_ptr on requeue proxy lock
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH v3] futex: update futex_q lock_ptr on requeue proxy lock
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• remembering rt-sched attributes - was: [LAD] rtirq script is broken with 2.6.31
  • From: Robin Gareus <robin@xxxxxxxxxx>
• Re: [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• [PATCH RT 7/6] include linux/interrupt.h in mm/bounce.c
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH RT 9/6] [RFH] Build failure on 2.6.31-rc4-rt1 in mm/highmem.c
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH RT 8/6] [ARM, WATCHDOG] davinci: include mach/timex.h in davinci_wdt.c
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Dave Young <hidave.darkstar@xxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• Re: [PATCH 2/6] s3c2443-ac97: convert semaphore to mutex
  • From: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Dave Young <hidave.darkstar@xxxxxxxxx>
• [PATCH V2] futex: Fix handling of bad requeue syscall pairing
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH] futex: Fix handling of bad requeue syscall pairing
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH] futex: Update futex_q lock_ptr on requeue proxy lock (resend)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• [PATCH 6/6] [ARM] Use atomic_spin_lock/atomic_spin_unlock for irqdesc lock
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [PATCH 6/6] [ARM] Use atomic_spin_lock/atomic_spin_unlock for irqdesc lock
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 1/6] ucb1x00: include linux/semaphore.h
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 3/6] [ARM] msm: include linux/cache.h in proc_comm.c
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 2/6] s3c2443-ac97: convert semaphore to mutex
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 5/6] [NET] ixp2000/enp2611: don't set non-existent member get_stats
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 4/6] [ARM] ixp2000: fix type of ixp2000_timer_interrupt
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• [PATCH 6/6] [ARM] Use atomic_spin_lock/atomic_spin_unlock for irqdesc lock
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [RT] Lockdep warning on boot with 2.6.31-rc5-rt1.1
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Sripathi Kodi <sripathik@xxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [PATCH 1/2] Update woken requeued futex_q lock_ptr
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
  • From: gowrishankar <gowrishankar.m@xxxxxxxxxxxxxxxxxx>
• Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
  • From: Sven-Thorsten Dietrich <sdietrich@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
  • From: John Kacur <jkacur@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
  • From: gowrishankar <gowrishankar.m@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] Update woken requeued futex_q lock_ptr
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH 2/2][RT] Avoid deadlock in rt_mutex_start_proxy_lock()
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH 1/2] Update woken requeued futex_q lock_ptr
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH 0/2] futex: requeue_pi lock steal deadlock fixes
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] linux-2.6.31-rc5-rt1.1
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Will Schmidt <will_schmidt@xxxxxxxxxxxx>
• [ANNOUNCE] linux-2.6.31-rc5-rt1.1
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: gowrishankar <gowrishankar.m@xxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: john stultz <johnstul@xxxxxxxxxx>
• 2.6.31-rc4-rt1: BUG: panic in requeue_pi test case
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: realtime measurement tests: approach to criteria
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: realtime measurement tests: approach to criteria
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• [ANNOUNCE] AlacrityVM hypervisor project
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Thomas Meyer <thomas@xxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• [PATCH V2] futex: futex_wait_requeue_pi commentary corrections
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [PATCH] futex: futex_wait_requeue_pi commentary corrections
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• [PATCH] futex: futex_wait_requeue_pi commentary corrections
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [PATCH][RT] stacktrace: dump out last preempt disable locations
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] 2.6.31-rc4-rt1: Convert xt_info_lock.lock to atomic_spinlock_t
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• [PATCH] 2.6.31-rc4-rt1: Convert xt_info_lock.lock to atomic_spinlock_t
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Clark Williams <williams@xxxxxxxxxx>
• 2.6.31-rc4-rt1: BUG: unable to handle kernel NULL pointer dereference at 0000006
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• [PATCH][RT] stacktrace: dump out last preempt disable locations
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Tim Blechmann <tim@xxxxxxxxxx>
• [ANNOUNCE] 2.6.31-rc4-rt1
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• BUG - kernel NULL pointer reference
  • From: Dennis Borgmann <dennis.borgmann@xxxxxxxxxxxxxx>
• Re: Real-Time Clocks and POSIX
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Real-Time Clocks and POSIX
  • From: "Pilhofer, Frank" <fpilhofe@xxxxxx>
• Re: SCHED_RR preempted by SCHED_OTHER
  • From: Denis Richard <denis.richard@xxxxxxxxxxxxxxxxx>
• Re: SCHED_RR preempted by SCHED_OTHER
  • From: "Luis Claudio R. Goncalves" <lclaudio@xxxxxxxx>
• Re: SCHED_RR preempted by SCHED_OTHER
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• SCHED_RR preempted by SCHED_OTHER
  • From: Denis Richard <denis.richard@xxxxxxxxxxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Stefan Agner <stefan.agner@xxxxxxxxx>
• Re: cpuinfo and HVM features
  • From: Avi Kivity <avi@xxxxxxxxxx>
• cpuinfo and HVM features (was: Host latency peaks due to kvm-intel)
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: cpuinfo and HVM features (was: Host latency peaks due to kvm-intel)
  • From: "Yang, Sheng" <sheng.yang@xxxxxxxxx>
• Re: geode-mfgpt oops 2.6.29.6-rt23
  • From: Jens Döring <j.doering@xxxxxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: "Yang, Sheng" <sheng.yang@xxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: "H. Peter Anvin" <h.peter.anvin@xxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Sbs <sbs.pub@xxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Sbs <sbs.pub@xxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: Doubt: Does RT patch reduce interrupt latency?
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Doubt: Does RT patch reduce interrupt latency?
  • From: Sbs <sbs.pub@xxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: [PATCH] A little spellchecking of the hwlat_detector.c file
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [PATCH] A little spellchecking of the hwlat_detector.c file
  • From: Jon Masters <jcm@xxxxxxxxxx>
• Re: geode-mfgpt oops 2.6.29.6-rt23
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Host latency peaks due to kvm-intel
  • From: Gregory Haskins <gregory.haskins@xxxxxxxxx>
• Host latency peaks due to kvm-intel
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• [PATCH] A little spellchecking of the hwlat_detector.c file
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Sound XRUN on RT-Linux
  • From: Dennis Borgmann <dennis.borgmann@xxxxxxxxxxxxxx>
• Re: i915_driver_irq_handler - BUG: NULL pointer dereference
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with hwlat detector in smp_processor_id()
  • From: John Kacur <jkacur@xxxxxxxxxx>
• i915_driver_irq_handler - BUG: NULL pointer dereference
  • From: John Kacur <jkacur@xxxxxxxxxx>
• geode-mfgpt oops 2.6.29.6-rt23
  • From: Jens Döring <j.doering@xxxxxxxxxxxx>
• [PATCH] show_stack_lvl smp_processor_id
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Gregory Haskins <ghaskins@xxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• i915 oopses w/ experimental rt kernel
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Michal Sojka <sojkam1@xxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Giuseppe Lipari <giuseppe.lipari@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Karthik Singaram Lakshmanan <karthiksingaram@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Karthik Singaram Lakshmanan <karthiksingaram@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "James H. Anderson" <anderson@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Test Scenario for Realtime latency benchmark in the worstcase environment.
  • From: GeunSik Lim <leemgs1@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Dhaval Giani <dhaval.giani@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Bjoern B. Brandenburg" <bbb@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "James H. Anderson" <anderson@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "James H. Anderson" <anderson@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "James H. Anderson" <anderson@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "James H. Anderson" <anderson@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Luca Abeni <lucabe72@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Jaswinder Singh Rajput <jaswinder@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Douglas Niehaus <niehaus@xxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Douglas Niehaus <niehaus@xxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: Kernel Panic with preempt RT patch 2.6.29.5-rt21
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Ted Baker <baker@xxxxxxxxxx>
• Re: Kernel Panic with preempt RT patch 2.6.29.5-rt21
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Noah Watkins <jayhawk@xxxxxxxxxxxx>
• Re: [PATCH] cyclictest: process option before checking for permissions
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: [PATCH] cyclictest: exit with an error code in error case
  • From: Clark Williams <williams@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Kernel Panic with preempt RT patch 2.6.29.5-rt21
  • From: Meha Mehta <mehtameha@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• [PATCH] cyclictest: process option before checking for permissions
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] cyclictest: exit with an error code in error case
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Raistlin <raistlin@xxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Douglas Niehaus <niehaus@xxxxxxxxxxx>
• Re: RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Fernando Lopez-Lezcano <nando@xxxxxxxxxxxxxxxxxx>
• RFC for a new Scheduling policy/class in the Linux-kernel
  • From: Henrik Austad <henrik@xxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Darren Hart <dvhltc@xxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.5-rt22
  • From: Fernando Lopez-Lezcano <nando@xxxxxxxxxxxxxxxxxx>
• Re: [ANNOUNCE] 2.6.29.6-rt23
  • From: Fernando Lopez-Lezcano <nando@xxxxxxxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Sripathi Kodi <sripathik@xxxxxxxxxx>
• i915_driver_irq_handler oops
  • From: John Kacur <jkacur@xxxxxxxxxx>
• Re: Test Scenario for Realtime latency benchmark in the worstcase environment.
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• [ANNOUNCE] 2.6.29.6-rt23
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Problem with hwlat detector in smp_processor_id()
  • From: Carsten Emde <Carsten.Emde@xxxxxxxxx>
• Re: Problem with hwlat detector in smp_processor_id()
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Problem with hwlat detector in smp_processor_id()
  • From: Wolfgang Steinwender <wolfgang@xxxxxxxxxxx>
• Re: hwlat latency readings [WAS: IRC Alert]
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• [PATCH] Group together irq patches in series file
  • From: Sven-Thorsten Dietrich <sven@xxxxxxxxxxxxxxxxxxxxx>
• Re: PREEMPT_RT + HIGHMEM = segfaults during boot on ppc32
  • From: Steve Rottinger <steve@xxxxxxxxxx>
• Re: hwlat latency readings [WAS: IRC Alert]
  • From: Jan Blunck <jblunck@xxxxxxxxx>
• Re: PREEMPT_RT + HIGHMEM = segfaults during boot on ppc32
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: Strange spikes using linux-rt kernel
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>
• Re: [LTP] LTP RT Tests (Cyclic, rt-migrate, etc)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• hwlat latency readings [WAS: IRC Alert]
  • From: Jon Masters <jonathan@xxxxxxxxxxxxxx>
• Re: Strange spikes using linux-rt kernel
  • From: Pedro R <eusou15@xxxxxxxxx>
• Re: Strange spikes using linux-rt kernel
  • From: Nicholas Mc Guire <mcguire@xxxxxxxxxx>
• Strange spikes using linux-rt kernel
  • From: Pedro R <eusou15@xxxxxxxxx>
• [PATCH]cyclictest: Arrange alphabetically for readability of "cyclictest --help".
  • From: GeunSik Lim <leemgs1@xxxxxxxxx>