From: Ulrich Obergfell <uobergfe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: dzickus@redhat.com, uobergfe@redhat.com
Subject: [PATCH v2 0/9] watchdog: parameters to control hard and soft lockup detector individually
Date: Fri, 17 Oct 2014 19:06:19 +0200 [thread overview]
Message-ID: <1413565588-4144-1-git-send-email-uobergfe@redhat.com> (raw)
This post follows up to https://lkml.org/lkml/2014/8/11/329.
During the discussion of that patch, Ingo Molnar commented in
https://lkml.org/lkml/2014/8/18/577.
"The softlockup and hardlockup detection control variables
should be in separate flags, inside and outside the kernel -
they (should) not relate to each other."
Please refer to [PATCH v2 7/9] for a description of the proposed
changes of the 'user interface' in /proc/sys/kernel and kernel
command line parameters.
There are no functional changes between the initial version in
https://lkml.org/lkml/2014/10/13/313 and v2. The new version is
merely a re-base to the following upstream commits.
commit 6e7458a6f074c71e74cda31c483114e65ea0f570
Author: Ulrich Obergfell <uobergfe@redhat.com>
Date: Mon Oct 13 15:55:35 2014 -0700
kernel/watchdog.c: control hard lockup detection default
commit 9919e39a17381058dd0cdef2f78dbf5619e26474
Author: Ulrich Obergfell <uobergfe@redhat.com>
Date: Mon Oct 13 15:55:37 2014 -0700
kvm: ensure hard lockup detection is disabled by default
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(-)
--
1.7.11.7
next reply other threads:[~2014-10-17 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 17:06 Ulrich Obergfell [this message]
2014-10-17 17:06 ` [PATCH v2 1/9] watchdog: new definitions and variables, initialization Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 2/9] watchdog: introduce the proc_watchdog_update() function Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 3/9] watchdog: move definition of 'watchdog_proc_mutex' outside of proc_dowatchdog() Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 4/9] watchdog: introduce the proc_watchdog_common() function Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 5/9] watchdog: introduce separate handlers for parameters in /proc/sys/kernel Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 6/9] watchdog: implement error handling for failure to set up hardware perf events Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 7/9] watchdog: enable the new user interface of the watchdog mechanism Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 8/9] watchdog: clean up some function names and arguments Ulrich Obergfell
2014-10-17 17:06 ` [PATCH v2 9/9] watchdog: introduce the hardlockup_detector_disable() function Ulrich Obergfell
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=1413565588-4144-1-git-send-email-uobergfe@redhat.com \
--to=uobergfe@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).