From: Laurence Oberman <loberman@redhat.com>
To: linux-kernel@vger.kernel.org, loberman@redhat.com
Cc: rdunlap@infradead.org, tglx@linutronix.de
Subject: [PATCH] V3 init/main.c Enable watchdog_thresh control from kernel line
Date: Wed, 24 Oct 2018 12:53:12 -0400 [thread overview]
Message-ID: <1540399992-23448-1-git-send-email-loberman@redhat.com> (raw)
Both graphics and serial consoles are exposed to hard lockups
when handling a large amount of messaging. The kernel watchdog_thresh
parameter up to now has not been available to be set on the kernel line for
early boot.
This patch allows the setting of watchdog_thresh to be increased
when needed to avoid the hard lockups in the console code.
Signed-off-by: Laurence Oberman <loberman@redhat.com>
---
Documentation/admin-guide/kernel-parameters.txt | 8 ++++++++
init/main.c | 9 +++++++++
2 files changed, 17 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 4cdcd1a..cd8d588 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -4932,6 +4932,14 @@
or other driver-specific files in the
Documentation/watchdog/ directory.
+ watchdog_thresh=
+ This parameter is now available as a kernel line
+ parameter. Use watchdog_thresh=30 as example
+ This will allow early boot changes of the current
+ default of 10s to be increased when needed to
+ avoid hard lockups.
+ Default: 10
+
workqueue.watchdog_thresh=
If CONFIG_WQ_WATCHDOG is configured, workqueue can
warn stall conditions and dump internal state to
diff --git a/init/main.c b/init/main.c
index 1c3f902..88cbed9 100644
--- a/init/main.c
+++ b/init/main.c
@@ -1038,6 +1038,15 @@ static int __init set_debug_rodata(char *str)
__setup("rodata=", set_debug_rodata);
#endif
+static int __init
+is_watchdog_thresh_setup(char *str)
+{
+ get_option(&str, &watchdog_thresh);
+ return 1;
+}
+__setup("watchdog_thresh=", is_watchdog_thresh_setup);
+
+
#ifdef CONFIG_STRICT_KERNEL_RWX
static void mark_readonly(void)
{
--
1.8.3.1
next reply other threads:[~2018-10-24 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 16:53 Laurence Oberman [this message]
2018-10-24 17:43 ` [PATCH] V3 init/main.c Enable watchdog_thresh control from kernel line Randy Dunlap
2018-10-24 18:23 ` kbuild test robot
2018-10-24 18:40 ` Laurence Oberman
2018-10-24 19:58 ` kbuild test robot
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=1540399992-23448-1-git-send-email-loberman@redhat.com \
--to=loberman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
/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).