summaryrefslogtreecommitdiff
path: root/drivers/bluetooth/btuart_cs.c
diff options
context:
space:
mode:
authorPeter Zijlstra <a.p.zijlstra@chello.nl>2011-07-19 22:07:25 (GMT)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2011-07-20 17:50:11 (GMT)
commitc5d753a55ac92e09816d410cd17093813f1a904b (patch)
tree162c63edcc463e18d50fb5b5be479785f02222c4 /drivers/bluetooth/btuart_cs.c
parent10f39bb1b2c1923ca73e70cb13aeee0e9b822d8f (diff)
downloadlinux-c5d753a55ac92e09816d410cd17093813f1a904b.tar.xz
sched: Add irq_{enter,exit}() to scheduler_ipi()
Ensure scheduler_ipi() calls irq_{enter,exit} when it does some actual work. Traditionally we never did any actual work from the resched IPI and all magic happened in the return from interrupt path. Now that we do do some work, we need to ensure irq_{enter,exit} are called so that we don't confuse things. This affects things like timekeeping, NO_HZ and RCU, basically everything with a hook in irq_enter/exit. Explicit examples of things going wrong are: sched_clock_cpu() -- has a callback when leaving NO_HZ state to take a new reading from GTOD and TSC. Without this callback, time is stuck in the past. RCU -- needs in_irq() to work in order to avoid some nasty deadlocks Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'drivers/bluetooth/btuart_cs.c')
0 files changed, 0 insertions, 0 deletions