From: Thomas Gleixner <tglx@linutronix.de>
To: Laurence Oberman <loberman@redhat.com>
Cc: linux-kernel@vger.kernel.org, rdunlap@infradead.org, prarit@redhat.com
Subject: Re: [PATCH] [PATCH V7] watchdog/core: Add watchdog_thresh command line parameter
Date: Thu, 1 Nov 2018 12:55:08 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1811011240310.1642@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1540911004-11539-1-git-send-email-loberman@redhat.com>
Laurence,
On Tue, 30 Oct 2018, Laurence Oberman wrote:
This looks much better.
But please send your patches first to yourself. Your subject ended up with
'[PATCH] [PATCH V7]' instead of just '[PATCH V7]'
> 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
kernel command line please. kernel line does not mean anything,
> early boot.
> This patch allows the setting of watchdog_thresh to be increased
Again:
git grep 'This patch' Documentation/process/
This leads you to:
"Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
to do frotz", as if you are giving orders to the codebase to change
its behaviour."
Documentation is there for a reason.
> 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 extend the hard lockup timer in the console code.
> Note that this also affects the soft lockup detector
Just for nitpickings sake. The change log is slightly confusing. Let me
give you a suggestion:
The hard and soft lockup detector threshold has a default value of 10
seconds which can only be changed via sysctl.
During early boot lockup detection can trigger when noisy debugging emits
a large amount of messages to the console, but there is no way to set a
larger threshold on the kernel command line. The detector can only be
completely disabled.
Add a new watchdog_thresh= command line parameter to allow boot time
control over the threshold. It works in the same way as the sysctl and
affects both the soft and the hard lockup detectors.
Hmm?
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4957,6 +4957,14 @@
> or other driver-specific files in the
> Documentation/watchdog/ directory.
>
> + watchdog_thresh=
Please use tabs instead of spaces
> + [KNL]
> + Set the hard lockup detector stall duration
> + threshold in seconds. The soft lockup detector
> + threshold is set to twice the value. A value of 0
> + disables both lockup detectors. Default is 10
> + seconds.
Same here.
Thanks,
tglx
prev parent reply other threads:[~2018-11-01 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 14:50 Laurence Oberman
2018-11-01 11:55 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1811011240310.1642@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=prarit@redhat.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®