On Thu, 16 Nov 2006 11:55:46 +0100 Mikael Pettersson <[EMAIL PROTECTED]> wrote:
> Andrew Morton writes: > > Surely the appropriate behaviour is to allow oprofile to steal the NMI and > > to then put the NMI back to doing the watchdog thing after oprofile has > > finished with it. > > Which is _exactly_ what pre-2.6.19-rc1 kernels did. I implemented > the in-kernel API allowing real performance counter drivers like > oprofile (and perfctr) to claim the HW from the NMI watchdog, > do their work, and then release it which resumed the watchdog. OK. But from Andi's comments it seems that the NMI watchdog was failing to resume its operation. > Note that oprofile (and perfctr) didn't do anything behind the > NMI watchdog's back. They went via the API. Nothing dodgy going on. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
