public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: josh@joshtriplett.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcutorture: Print out barrier error as document says
Date: Sat, 13 Aug 2016 19:40:22 -0700	[thread overview]
Message-ID: <20160814024022.GH3482@linux.vnet.ibm.com> (raw)
In-Reply-To: <1471071275-12671-1-git-send-email-sj38.park@gmail.com>

On Sat, Aug 13, 2016 at 03:54:35PM +0900, SeongJae Park wrote:
> Test for rcu_barrier() has introduced by commit fae4b54f28f0 ("rcu:
> Introduce rcutorture testing for rcu_barrier()").  Updated document says
> that `rtbe` field of output indicates failure of the test.  However, the
> code has not updated as so.  This commit updates the code to print out
> the field as document says.
> 
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good catch, queue!

						Thanx, Paul

> ---
>  kernel/rcu/rcutorture.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
> index f0f32f8..ac29017 100644
> --- a/kernel/rcu/rcutorture.c
> +++ b/kernel/rcu/rcutorture.c
> @@ -1259,8 +1259,9 @@ rcu_torture_stats_print(void)
>  		atomic_read(&n_rcu_torture_alloc),
>  		atomic_read(&n_rcu_torture_alloc_fail),
>  		atomic_read(&n_rcu_torture_free));
> -	pr_cont("rtmbe: %d rtbke: %ld rtbre: %ld ",
> +	pr_cont("rtmbe: %d rtbe: %ld rtbke: %ld rtbre: %ld ",
>  		atomic_read(&n_rcu_torture_mberror),
> +		n_rcu_torture_barrier_error,
>  		n_rcu_torture_boost_ktrerror,
>  		n_rcu_torture_boost_rterror);
>  	pr_cont("rtbf: %ld rtb: %ld nt: %ld ",
> -- 
> 1.9.1
> 

      reply	other threads:[~2016-08-14  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13  6:54 [PATCH] rcutorture: Print out barrier error as document says SeongJae Park
2016-08-14  2:40 ` Paul E. McKenney [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=20160814024022.GH3482@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    /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