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. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
