[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120221175810.GA10708@linux.vnet.ibm.com>
Date: Tue, 21 Feb 2012 09:58:11 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...ymtl.ca,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
fweisbec@...il.com, patches@...aro.org
Subject: [PATCH tip/core/rcu 0/4] Additional RCU commits for 3.4
Hello!
This series contains an additional four commits for 3.4. They are all
small fixes. This series is in addition to the set posted earlier at
https://lkml.org/lkml/2012/2/3/459, and there is some possibility that
the direct-drive SRCU at https://lkml.org/lkml/2012/2/12/117 will also
make it. The four new patches are as follows:
1. Fix RCU_FAST_NO_HZ to avoid continually retrying dyntick-idle
entry if softirqs are pending.
2. Fix RCU_FAST_NO_HZ to avoid retrying dyntick-idle entry when
idle is re-entered after a timer was posted. For both #1 and
#2, the philosophy is that it is better to take a scheduling-clock
interrupt than to burn lots of CPU in a futile attempt to process
RCU callbacks.
3. Eliminate spurious warnings from synchronize_sched_expedited(),
courtesy of Hugh Dickens.
4. Apply several fixes to rcutorture based on initial inspection.
For a testing-only version of this patchset from git, please see the
following subject-to-rebase branch:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
Thanx, Paul
------------------------------------------------------------------------
b/kernel/rcutorture.c | 19 ++++++++++++++++---
b/kernel/rcutree.c | 2 +-
b/kernel/rcutree_plugin.h | 3 ++-
kernel/rcutree.c | 2 +-
kernel/rcutree_plugin.h | 2 +-
5 files changed, 21 insertions(+), 7 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists