public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: [ANNOUNCE] 3.0.1-rt8
Date: Tue, 09 Aug 2011 11:31:46 -0700	[thread overview]
Message-ID: <4E417D12.70608@localhost> (raw)
In-Reply-To: <1312580681.28695.44.camel@twins>

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.

-- 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-09 18:31 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 ` Fernando Lopez-Lezcano [this message]
2011-08-09 18:47   ` [ANNOUNCE] 3.0.1-rt8 Peter Zijlstra
2011-08-10  1:08     ` Paul E. McKenney
2011-08-10  1:07   ` Paul E. McKenney

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=4E417D12.70608@localhost \
    --to=nando@ccrma.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --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