linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	Clark Williams <williams@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>, Carsten Emde <ce@ceag.ch>
Subject: Re: 2.6.26-rt1
Date: Fri, 1 Aug 2008 14:11:14 -0700	[thread overview]
Message-ID: <20080801211114.GC14851@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807300006180.14925@apollo.tec.linutronix.de>

On Wed, Jul 30, 2008 at 12:21:10AM +0200, Thomas Gleixner wrote:
> We are pleased to announce the 2.6.26-rt1 tree, which can be
> downloaded from the location:
>   
>    http://rt.et.redhat.com/download/
> 
> Information on the RT patch can be found at:
> 
>    http://rt.wiki.kernel.org/index.php/Main_Page
> 
> The merge was mostly done by Steven Rostedt, I just fixed it up, added
> the fixes from .24-rt17 and tested it on x86 32/64bit.
> 
> This is the first cut of .26-rt, so don't expect it to be perfect.
> 
> I run out of time, so I dropped Peter's cpu-hotplug patches
> completely. The hotplug and rcupreempt code has changed radically, so
> we need to redo that lot. Peter, Paul can you please look into that ?
> 
> I tried to address the non-x86 issues as far as I could, but I had no
> chance to compile test them. So please check the wreckage.
> 
> to build a 2.6.26-rt1 tree, the following patches should be applied:
> 
>    http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
>    http://rt.et.redhat.com/download/patch-2.6.26-rt1.bz2
>   
> And like always, Steven's RT version of Matt Mackall's ketchup will get this
> for you nicely:
> 
>   http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
> 
> As usual the broken out patches are also available.
> 
> I'm going on vacation tomorrow so feel free to blame/curse/flame me,
> but please work with Steven to get it into shape.

Hmmm...  Still quite a few RCU-related patches in there.  Here is my
kneejerk reaction on what to do about them:

o	call_rcu_bh-rename-of-call_rcu.patch should go to mainline.

o	rcu-trace-fix-free.patch should go to mainline.

o	rcu-preempt-fix-bad-dyntick-accounting.patch can be dropped
	from -rt without going to mainline.

o	Some of rcu-hrt-fixups.patch needs to go over, some need to
	come back:

	o	__rcu_process_callbacks() change of local_irq_disable()
		to local_irq_save() should go to mainline.

	o	-rt needs to take the change that dropped the parameter
		for softirq functions.

	o	-rt needs to take the change of rcu_process_callbacks()
		to static (both declaration and definition).

	o	-rt needs to take the deletion of rcu_advance_callbacks()

o	rcu-new-7.patch needs to move over (torture preemptable RCU)
	Ditto for rcu-torture-preempt-update.patch.  But not blazingly
	urgent.

o	RCU boosting needs re-implementation, in the works.

o	preempt_realtime_rcu.patch is mostly about raw_spinlock_t.
	Is mainline's raw_spinlock_t compatible with that of -rt?
	If so, this should go to mainline.

o	rcu-preempt-hotplug-hackaround.patch should be able to be
	dropped at some point (maybe even as of 2.6.26?).

Thoughts?

							Thanx, Paul

  parent reply	other threads:[~2008-08-01 21:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 20:09 2.6.24.7-rt15 Thomas Gleixner
2008-07-26 11:03 ` 2.6.24.7-rt15 Carsten Emde
     [not found] ` <1985e0f60807252248n581bdfa0s363f6ce0d283ec2c@mail.gmail.com>
2008-07-26 11:13   ` 2.6.24.7-rt15 Jaswinder Singh
2008-07-26 12:28     ` 2.6.24.7-rt15 Steven Rostedt
2008-07-26 13:22       ` 2.6.24.7-rt15 Daniel Walker
2008-07-26 18:28       ` 2.6.24.7-rt15 Jaswinder Singh
2008-07-27 16:16 ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-27 20:28   ` 2.6.24.7-rt16 Avuton Olrich
2008-07-27 20:37     ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-28  8:12   ` 2.6.24.7-rt16 Wolfgang Grandegger
2008-07-28  9:48     ` 2.6.24.7-rt16 Peter Zijlstra
2008-07-28 10:12       ` 2.6.24.7-rt16 Wolfgang Grandegger
2008-07-29 12:57   ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-29 22:21     ` 2.6.26-rt1 Thomas Gleixner
2008-07-30  9:01       ` 2.6.26-rt1 Jürgen Mell
2008-07-30 17:18         ` [PATCH] Fix Bug messages Chirag Jog
2008-07-30 20:16           ` Jürgen Mell
2008-07-31  6:06           ` Peter Zijlstra
2008-07-31  8:00           ` Sebastien Dugue
2008-07-31 10:13             ` John Kacur
2008-07-31 11:23               ` Sebastien Dugue
2008-07-31 13:49                 ` John Kacur
2008-07-31 14:01                   ` Peter Zijlstra
2008-07-31 14:10                     ` John Kacur
2008-07-31 14:18                       ` Peter Zijlstra
2008-07-31 14:35                     ` Sebastien Dugue
2008-07-31 15:01                       ` Clark Williams
2008-07-31 15:14                         ` Sebastien Dugue
2008-08-01 21:11         ` 2.6.26-rt1 Paul E. McKenney
2008-08-13 13:30           ` 2.6.26-rt1 Juergen Beisert
2008-08-13 16:37             ` 2.6.26-rt1 Paul E. McKenney
2008-07-30 14:31       ` 2.6.26-rt1 John Kacur
2008-07-30 14:41       ` 2.6.26-rt1 Ryan Hope
2008-08-01 21:11       ` Paul E. McKenney [this message]
2008-08-11  8:36       ` 2.6.26-rt1 Juergen Beisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080801211114.GC14851@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=ce@ceag.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).