> One thing: since we have the unnatural relationship between the watchdog
> and oprofile, I would much prefer that be obvious in the priority. e.g
> MAX_NMI_PRIORITY, which oprofile uses, then watchdog is MAX_NMI_PRIORITY
> -1. Currently the gap between the two values you use indicates it's OK
> to have another handler inbetween, which it definitely isn't.
Hmm how about when the machine really is in trouble, we really wouldn't
want some things to be running when we want the watchdog to trigger. How
do you propose we handle this? nmi_watchdog_tick is pretty light so it has
a lesser chance of blowing up in various code when the machine is on the
brink of death.
150,000? Nice Corey, again i stand corrected on that front.
Zwane
-- function.linuxpower.ca- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/