Hi Andrew, Poke. What can I do to move this patch forward?
Cheers, Don On Tue, Nov 04, 2014 at 11:20:15AM -0500, Don Zickus wrote: > The hardlockup and softockup had always been tied together. Due to the > request > of KVM folks, they had a need to have one enabled but not the other. > Internally rework the code to split things apart more cleanly. > > There is a bunch of churn here, but the end result should be code that should > be easier to maintain and fix without knowing the internals of what is going > on. > > Tested by Uli and myself. > > Ulrich Obergfell (9): > watchdog: new definitions and variables, initialization > watchdog: introduce the proc_watchdog_update() function > watchdog: move definition of 'watchdog_proc_mutex' outside of > proc_dowatchdog() > watchdog: introduce the proc_watchdog_common() function > watchdog: introduce separate handlers for parameters in > /proc/sys/kernel > watchdog: implement error handling for failure to set up hardware > perf events > watchdog: enable the new user interface of the watchdog mechanism > watchdog: clean up some function names and arguments > watchdog: introduce the hardlockup_detector_disable() function > > arch/x86/kernel/kvm.c | 2 +- > include/linux/nmi.h | 21 ++-- > kernel/sysctl.c | 35 +++++-- > kernel/watchdog.c | 277 > ++++++++++++++++++++++++++++++++++++------------- > 4 files changed, 240 insertions(+), 95 deletions(-) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
