Skip to contentSkip to conversation

perfctr ppc32 preliminary interrupt support

PATCH Albert Cahalan 2 participants 2 messages Sep 27, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines · Benjamin Herrenschmidt

Be careful that some G4's have a bug which can cause a perf monitor interrupt to crash your kernel :( Basically, the problem is if any of TAU or PerfMon interrupt happens at the same time as a DEC interrupt, some revs of the CPU can get confused and lose the previous exception state.

Instead of excluding all these CPUs, simply put the clock tick on the PerfMon interrupt. There's a bit-flip that'll go at about 4 kHz on a system with a 100 MHz bus. That should do. One need not change HZ; the interrupt can be ignored whenever the timebase hasn't advanced enough to require another clock tick.

#1 lore raw
Quoted 8 lines · Albert Cahalan
Quoted 5 lines · Benjamin Herrenschmidt

Be careful that some G4's have a bug which can cause a perf monitor interrupt to crash your kernel :( Basically, the problem is if any of TAU or PerfMon interrupt happens at the same time as a DEC interrupt, some revs of the CPU can get confused and lose the previous exception state.

Quoted 6 lines

Instead of excluding all these CPUs, simply put the clock tick on the PerfMon interrupt. There's a bit-flip that'll go at about 4 kHz on a system with a 100 MHz bus. That should do. One need not change HZ; the interrupt can be ignored whenever the timebase hasn't advanced enough to require another clock tick.

True, we can use the perfmon instead of the DEC for those

Ben.