mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zqiang <qiang1.zhang@intel.com>
Cc: frederic@kernel.org, joel@joelfernandes.org, rcu@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu-tasks: Use accurate runstart time for RCU Tasks boot-time testing
Date: Mon, 21 Nov 2022 17:30:19 -0800	[thread overview]
Message-ID: <20221122013019.GW4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20221121150150.319715-1-qiang1.zhang@intel.com>

On Mon, Nov 21, 2022 at 11:01:50PM +0800, Zqiang wrote:
> Currently, only get jiffies once as the runstart time for all RCU
> Tasks testing. it's not accurate, for each RCU Tasks type test, since
> corresponding type of synchronize_rcu_tasks*() be invoked, so before
> each RCU Tasks test starts, we need to wait for the grace period of
> the previous RCU Tasks test to end, there will be a deviation in the
> start time of the RCU Tasks test.
> 
> Therefore, this commit at the start of each RCU Tasks test, re-fetch the
> jiffies time as the runstart time.
> 
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>

Good catch!  Applied with the usual wordsmithing, so please do check.

							Thanx, Paul

> ---
>  kernel/rcu/tasks.h | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h
> index b0b885e071fa..4a991311be9b 100644
> --- a/kernel/rcu/tasks.h
> +++ b/kernel/rcu/tasks.h
> @@ -1813,23 +1813,21 @@ static void test_rcu_tasks_callback(struct rcu_head *rhp)
>  
>  static void rcu_tasks_initiate_self_tests(void)
>  {
> -	unsigned long j = jiffies;
> -
>  	pr_info("Running RCU-tasks wait API self tests\n");
>  #ifdef CONFIG_TASKS_RCU
> -	tests[0].runstart = j;
> +	tests[0].runstart = jiffies;
>  	synchronize_rcu_tasks();
>  	call_rcu_tasks(&tests[0].rh, test_rcu_tasks_callback);
>  #endif
>  
>  #ifdef CONFIG_TASKS_RUDE_RCU
> -	tests[1].runstart = j;
> +	tests[1].runstart = jiffies;
>  	synchronize_rcu_tasks_rude();
>  	call_rcu_tasks_rude(&tests[1].rh, test_rcu_tasks_callback);
>  #endif
>  
>  #ifdef CONFIG_TASKS_TRACE_RCU
> -	tests[2].runstart = j;
> +	tests[2].runstart = jiffies;
>  	synchronize_rcu_tasks_trace();
>  	call_rcu_tasks_trace(&tests[2].rh, test_rcu_tasks_callback);
>  #endif
> -- 
> 2.25.1
> 

      reply	other threads:[~2022-11-22  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 15:01 Zqiang
2022-11-22  1:30 ` 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=20221122013019.GW4001@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiang1.zhang@intel.com \
    --cc=rcu@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 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®