From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: [ANNOUNCE] 3.0-rt4 Date: Thu, 28 Jul 2011 11:32:07 -0700 Message-ID: <20110728183207.GR2403@linux.vnet.ibm.com> References: <20110728174123.GA10751@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: LKML , linux-rt-users , Peter Zijlstra , Steven Rostedt , Jason Wessel To: Thomas Gleixner Return-path: Received: from e2.ny.us.ibm.com ([32.97.182.142]:50852 "EHLO e2.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754947Ab1G1Sd1 (ORCPT ); Thu, 28 Jul 2011 14:33:27 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Thu, Jul 28, 2011 at 07:43:43PM +0200, Thomas Gleixner wrote: > > On Thu, 28 Jul 2011, Paul E. McKenney wrote: > > > On Wed, Jul 27, 2011 at 11:37:09PM +0200, Thomas Gleixner wrote: > > > Dear RT Folks, > > > > > > I'm pleased to announce the 3.0-rt4 release. > > > > 3.0-rt5 boots single-CPU under KVM on a 32-bit laptop. Also with "-smp > > 2". It even survived a minute or so of rcutorture in both cases. ;-) > > > > Some weirdness with interactivity -- if the system is idle aside from > > rcutorture, the rcutorture.stat_interval console messages don't come > > out unless I hit "enter" on the console. But if I run "top", they do > > come out regularly. Might well be KVM's fault, except that running > > rcutorture on non-rt kernels doesn't exhibit this behavior. > > Nah, that's my lazy "avoid printing from atomic context" hack :) Well, then, that does seem to be working... ;-) Except that these printk()s are from process level -- rcu_torture_stats() in kernel/rcutorture.c. > > I guess I should try RCU_BOOST=y, then... > > Good luck :) Compiled without error and has been running rcutorture smp=2 for about 30 minutes now. Thanx, Paul