Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)

[Mikael Pettersson]

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.

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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/