summaryrefslogtreecommitdiffstats
path: root/kernel/sched.c
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2009-02-05 15:23:08 +0100
committerIngo Molnar <mingo@elte.hu>2009-02-05 15:24:14 +0100
commit82aa9a1829199233f9bdaf26e2ee271114f4701e (patch)
tree638cccf1b1708bdce1cc45d54408c0907f051128 /kernel/sched.c
parent5b75af0a02fcf3b8899f38ff6f22164c5d8e2fdd (diff)
downloadop-kernel-dev-82aa9a1829199233f9bdaf26e2ee271114f4701e.zip
op-kernel-dev-82aa9a1829199233f9bdaf26e2ee271114f4701e.tar.gz
perfcounters: fix "perf counters kills oprofile" bug, v2
Impact: fix kernel crash Both oprofile and perfcounters register an NMI die handler, but only one can handle the NMI. Conveniently, oprofile unregisters it's notifier when not actively in use, so setting it's notifier priority higher than perfcounter's allows oprofile to borrow the NMI for the duration of it's run. Tested/works both as module and built-in. While testing, I found that if kerneltop was generating NMIs at very high frequency, the kernel may panic when oprofile registered it's handler. This turned out to be because oprofile registers it's handler before reset_value has been allocated, so if an NMI comes in while it's still setting up, kabOom. Rather than try more invasive changes, I followed the lead of other places in op_model_ppro.c, and simply returned in that highly unlikely event. (debug warnings attached) Signed-off-by: Mike Galbraith <efault@gmx.de> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/sched.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud