[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1458209675-177377-1-git-send-email-anna-maria@linutronix.de>
Date: Thu, 17 Mar 2016 11:14:35 +0100
From: Anna-Maria Gleixner <anna-maria@...utronix.de>
To: linux-kernel@...r.kernel.org
Cc: rt@...utronix.de, Anna-Maria Gleixner <anna-maria@...utronix.de>,
Josh Triplett <josh@...htriplett.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: rcutorture: Consider FROZEN hotplug notifier transitions
The hotplug notifier rcutorture_cpu_notify() doesn't consider the
corresponding CPU_XXX_FROZEN transitions. They occure on
suspend/resume and are usually handled the same way as the
corresponding non frozen transitions.
Mask the switch case action argument with '~CPU_TASKS_FROZEN' to map
CPU_XXX_FROZEN hotplug transitions on corresponding non frozen
transitions.
Cc: Josh Triplett <josh@...htriplett.org>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Signed-off-by: Anna-Maria Gleixner <anna-maria@...utronix.de>
---
kernel/rcu/rcutorture.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/rcu/rcutorture.c
+++ b/kernel/rcu/rcutorture.c
@@ -1598,7 +1598,7 @@ static int rcutorture_cpu_notify(struct
{
long cpu = (long)hcpu;
- switch (action) {
+ switch (action & ~CPU_TASKS_FROZEN) {
case CPU_ONLINE:
case CPU_DOWN_FAILED:
(void)rcutorture_booster_init(cpu);
Powered by blists - more mailing lists