From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH] doc: correct parameter in stallwarn
Date: Tue, 30 Oct 2018 05:45:55 -0700 [thread overview]
Message-ID: <20181030124555.GD4170@linux.ibm.com> (raw)
In-Reply-To: <20181030051559.256849-1-joel@joelfernandes.org>
On Mon, Oct 29, 2018 at 10:15:59PM -0700, Joel Fernandes (Google) wrote:
> The stallwarn document incorrectly mentions 'fps=' instead of 'fqs='.
> Correct that.
>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Good catch, queued, thank you!
Thanx, Paul
> ---
> Documentation/RCU/stallwarn.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/stallwarn.txt b/Documentation/RCU/stallwarn.txt
> index b01bcafc64aa..073dbc12d1ea 100644
> --- a/Documentation/RCU/stallwarn.txt
> +++ b/Documentation/RCU/stallwarn.txt
> @@ -205,7 +205,7 @@ handlers are no longer able to execute on this CPU. This can happen if
> the stalled CPU is spinning with interrupts are disabled, or, in -rt
> kernels, if a high-priority process is starving RCU's softirq handler.
>
> -The "fps=" shows the number of force-quiescent-state idle/offline
> +The "fqs=" shows the number of force-quiescent-state idle/offline
> detection passes that the grace-period kthread has made across this
> CPU since the last time that this CPU noted the beginning of a grace
> period.
> --
> 2.19.1.568.g152ad8e336-goog
>
next prev parent reply other threads:[~2018-10-30 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 5:15 [PATCH] doc: correct parameter in stallwarn Joel Fernandes (Google)
2018-10-30 12:45 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 5:15 Joel Fernandes (Google)
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=20181030124555.GD4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.