public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Fernando Lopez-Lezcano <nando@ccrma.stanford.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8
Date: Tue, 9 Aug 2011 18:07:45 -0700	[thread overview]
Message-ID: <20110810010745.GB2737@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E417D12.70608@localhost>

On Tue, Aug 09, 2011 at 11:31:46AM -0700, Fernando Lopez-Lezcano wrote:
> On 08/05/2011 02:44 PM, Peter Zijlstra wrote:
> >Hi,
> >
> >Since yesterday is old, and yesterday's kernels aren't interesting,
> >here's a fresh one: 3.0.1-rt8.
> 
> Hmmm, what are reasonable values for CONFIG_RCU_BOOST_PRIO and
> CONFIG_RCU_BOOST_DELAY? (or at least what are you using?). I think
> CONFIG_RCU_BOOST should be working now so I should reenable the
> option for my next build.

I use the defaults, except when verifying that I can change them.  ;-)

							Thanx, Paul

> -- Fernando
> 
> 
> >Aside from the obvious rebase to 3.0.1 changes include:
> >
> >  - a fix from Rostedt for his cpupri rework involving memory ordering
> >  - a fix from me regarding this highmem muck, seeing as I mostly
> >    wrecked things last time around :-)
> >  - some lockdep annotations from upstream for things people were
> >    seeing here as well
> >  - a patch from Clark adding a sysfs file to recognize a PREEMP_RT
> >    kernel for udev -- is there really no saner solution !?
> >  - and a fresh raw_spinlock_t conversion of cpufreq_driver_lock, done
> >    just minutes before releasing this, to keep life interesting.
> >
> >Still working on the known issues from last time..
> >
> >The patch is at:
> >
> >   http://www.kernel.org/pub/linux/kernel/projects/rt/patch-3.0.1-rt8.patch.bz2
> >
> >The quilt series can be found here:
> >
> >   http://www.kernel.org/pub/linux/kernel/projects/rt/patches-3.0.1-rt8.tar.bz2
> >
> >Once kernel.org mirrors catch up that is..

      parent reply	other threads:[~2011-08-10  1:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 21:44 [ANNOUNCE] 3.0.1-rt8 Peter Zijlstra
2011-08-09 15:13 ` [ANNOUNCE] 3.0.1-rt8 - Regression to 3.0-rt7 Tim Sander
2011-08-11  9:43   ` Peter Zijlstra
2011-08-11 11:30     ` Tim Sander
2011-08-11 12:02       ` Peter Zijlstra
2011-08-11 12:52         ` Tim Sander
2011-08-11 15:28         ` Tim Sander
2011-08-11 12:41       ` Peter Zijlstra
2011-08-11 16:04         ` Tim Sander
2011-08-11 16:14           ` Peter Zijlstra
2011-08-11 16:22             ` Tim Sander
2011-08-11 16:41               ` Tim Sander
2011-08-11 16:39           ` Peter Zijlstra
2011-08-11 17:08             ` Tim Sander
2011-08-11 18:05           ` Peter Zijlstra
2011-08-12  8:59             ` Tim Sander
2011-08-11 10:45   ` Peter Zijlstra
2011-08-11 15:36     ` Tim Sander
2011-08-09 18:31 ` [ANNOUNCE] 3.0.1-rt8 Fernando Lopez-Lezcano
2011-08-09 18:47   ` Peter Zijlstra
2011-08-10  1:08     ` Paul E. McKenney
2011-08-10  1:07   ` Paul E. McKenney [this message]

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=20110810010745.GB2737@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.stanford.edu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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