> Sounds like you have a fundamentally incompatible set of requirements.
Sounds so yep :) > Why do you need the softlockup watchdog if you intend to induce soft > lockups on purpose? It's a condition of a customer of us, so I can't change it. But it happens not often that my part is used. So I thought there is a mechanism to disable or reset the watchdog because it is a legal pause for it. And there is one "touch_softlockup_watchdog()", that does what I want, BUT just for the current cpu. And so the watchdog blats from the other cpu. Thilo - 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/
