From: tip-bot for Aaron Tomlin <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
atomlin@redhat.com, tglx@linutronix.de
Subject: [tip:core/urgent] hung_task/Documentation: Fix hung_task_warnings description
Date: Fri, 31 Jan 2014 00:45:33 -0800 [thread overview]
Message-ID: <tip-70e0ac5f3683f48a8174a6f231a0f3097217c189@git.kernel.org> (raw)
Commit-ID: 70e0ac5f3683f48a8174a6f231a0f3097217c189
Gitweb: http://git.kernel.org/tip/70e0ac5f3683f48a8174a6f231a0f3097217c189
Author: Aaron Tomlin <atomlin@redhat.com>
AuthorDate: Mon, 27 Jan 2014 09:00:57 +0000
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 31 Jan 2014 09:24:03 +0100
hung_task/Documentation: Fix hung_task_warnings description
Improve the documentation on hung_task_warnings.
Signed-off-by: Aaron Tomlin <atomlin@redhat.com>
Link: http://lkml.kernel.org/n/tip-xepjnxzummfDlg9lvhh7Rlzc@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/sysctl/kernel.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index 4205f3c..621c56c 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -319,10 +319,11 @@ This file shows up if CONFIG_DETECT_HUNG_TASK is enabled.
==============================================================
-hung_task_warning:
+hung_task_warnings:
The maximum number of warnings to report. During a check interval
-When this value is reached, no more the warnings will be reported.
+if a hung task is detected, this value is decreased by 1.
+When this value reaches 0, no more warnings will be reported.
This file shows up if CONFIG_DETECT_HUNG_TASK is enabled.
-1: report an infinite number of warnings.
reply other threads:[~2014-01-31 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tip-70e0ac5f3683f48a8174a6f231a0f3097217c189@git.kernel.org \
--to=tipbot@zytor.com \
--cc=atomlin@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome