Searched hist:"3 a6cb58f159e64241b2af9374acad41a70939349" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | torture.h | diff 3a6cb58f159e64241b2af9374acad41a70939349 Mon Dec 10 11:44:52 CST 2018 Paul E. McKenney <paulmck@linux.ibm.com> rcutorture: Add grace period after CPU offline
Beyond a certain point in the CPU-hotplug offline process, timers get
stranded on the outgoing CPU, and won't fire until that CPU comes back
online, which might well be never. This commit therefore adds a hook
in torture_onoff_init() that is invoked from torture_offline(), which
rcutorture uses to occasionally wait for a grace period. This should
result in failures for RCU implementations that rely on stranded timers
eventually firing in the absence of the CPU coming back online.
Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
|
| /openbmc/linux/kernel/ |
| H A D | torture.c | diff 3a6cb58f159e64241b2af9374acad41a70939349 Mon Dec 10 11:44:52 CST 2018 Paul E. McKenney <paulmck@linux.ibm.com> rcutorture: Add grace period after CPU offline
Beyond a certain point in the CPU-hotplug offline process, timers get
stranded on the outgoing CPU, and won't fire until that CPU comes back
online, which might well be never. This commit therefore adds a hook
in torture_onoff_init() that is invoked from torture_offline(), which
rcutorture uses to occasionally wait for a grace period. This should
result in failures for RCU implementations that rely on stranded timers
eventually firing in the absence of the CPU coming back online.
Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
|
| /openbmc/linux/kernel/locking/ |
| H A D | locktorture.c | diff 3a6cb58f159e64241b2af9374acad41a70939349 Mon Dec 10 11:44:52 CST 2018 Paul E. McKenney <paulmck@linux.ibm.com> rcutorture: Add grace period after CPU offline
Beyond a certain point in the CPU-hotplug offline process, timers get
stranded on the outgoing CPU, and won't fire until that CPU comes back
online, which might well be never. This commit therefore adds a hook
in torture_onoff_init() that is invoked from torture_offline(), which
rcutorture uses to occasionally wait for a grace period. This should
result in failures for RCU implementations that rely on stranded timers
eventually firing in the absence of the CPU coming back online.
Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
|
| /openbmc/linux/kernel/rcu/ |
| H A D | rcutorture.c | diff 3a6cb58f159e64241b2af9374acad41a70939349 Mon Dec 10 11:44:52 CST 2018 Paul E. McKenney <paulmck@linux.ibm.com> rcutorture: Add grace period after CPU offline
Beyond a certain point in the CPU-hotplug offline process, timers get
stranded on the outgoing CPU, and won't fire until that CPU comes back
online, which might well be never. This commit therefore adds a hook
in torture_onoff_init() that is invoked from torture_offline(), which
rcutorture uses to occasionally wait for a grace period. This should
result in failures for RCU implementations that rely on stranded timers
eventually firing in the absence of the CPU coming back online.
Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
|