From: Don Zickus <dzickus@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
uobergfe@redhat.com, Don Zickus <dzickus@redhat.com>
Subject: [PATCH 0/9] watchdog: internally split softlockup and hardlockup
Date: Tue, 4 Nov 2014 11:20:15 -0500 [thread overview]
Message-ID: <1415118024-194247-1-git-send-email-dzickus@redhat.com> (raw)
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(-)
next reply other threads:[~2014-11-04 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:20 Don Zickus [this message]
2014-11-04 16:20 ` [PATCH 1/9] watchdog: new definitions and variables, initialization Don Zickus
2014-11-04 16:20 ` [PATCH 2/9] watchdog: introduce the proc_watchdog_update() function Don Zickus
2014-11-04 16:20 ` [PATCH 3/9] watchdog: move definition of 'watchdog_proc_mutex' outside of proc_dowatchdog() Don Zickus
2014-11-04 16:20 ` [PATCH 4/9] watchdog: introduce the proc_watchdog_common() function Don Zickus
2014-11-04 16:20 ` [PATCH 5/9] watchdog: introduce separate handlers for parameters in /proc/sys/kernel Don Zickus
2014-11-04 16:20 ` [PATCH 6/9] watchdog: implement error handling for failure to set up hardware perf events Don Zickus
2014-11-04 16:20 ` [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism Don Zickus
2014-11-04 16:20 ` [PATCH 8/9] watchdog: clean up some function names and arguments Don Zickus
2014-11-04 16:20 ` [PATCH 9/9] watchdog: introduce the hardlockup_detector_disable() function Don Zickus
2014-12-17 21:25 ` [PATCH 0/9] watchdog: internally split softlockup and hardlockup Don Zickus
2015-01-21 14:15 ` Don Zickus
2015-01-21 22:23 ` Andrew Morton
2015-02-05 20:40 Don Zickus
2015-02-05 23:22 ` Andrew Morton
2015-02-06 14:12 ` Don Zickus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1415118024-194247-1-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=uobergfe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome