mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: paulmck@linux.vnet.ibm.com
Cc: jiangshanlai@gmail.com, josh@joshtriplett.org,
	rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, kernel-team@lge.com,
	joel@joelfernandes.org
Subject: Re: [PATCH] rcu: Report a quiescent state of TASKS_RCU on a tick from user
Date: Tue, 15 May 2018 13:19:17 +0900	[thread overview]
Message-ID: <28cb032c-1c44-41b2-4703-e6f942d073de@lge.com> (raw)
In-Reply-To: <20180515041111.GC26088@linux.vnet.ibm.com>



On 2018-05-15 13:11, Paul E. McKenney wrote:
> On Tue, May 15, 2018 at 09:33:46AM +0900, Byungchul Park wrote:
>> Hello Paul,
>>
>> You removed the reporing while simplifying the commit 508880df6 :)
>> Fold this patch onto the commit or add, whatever you want.
> 
> First, thank you for checking!
> 
> But second, the removal was intentional.  Tiny RCU only exists in
> PREEMPT=n kernels, and in such kernels there can be no RCU-tasks.
> This is the reason for this line in the new commit log:

I see. Thank you.

> [ paulmck: Simplify rcutiny portion given no RCU-tasks for !PREEMPT. ]
> 
> 							Thanx, Paul
> 
>> Thanks,
>> Byungchul
>>
>> ----->8-----
>> >From 18a2d8da3baf79d0edd5ccf94abe6f989da5b1c1 Mon Sep 17 00:00:00 2001
>> From: Byungchul Park <byungchul.park@lge.com>
>> Date: Tue, 15 May 2018 09:21:43 +0900
>> Subject: [PATCH] rcu: Report a quiescent state of TASKS_RCU on a tick from
>>   user
>>
>> The reporting was removed while simplifying the commit 508880df6 (rcu:
>> Improve rcu_note_voluntary_context_switch() reporting). Add it back.
>>
>> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
>> ---
>>   kernel/rcu/tiny.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/rcu/tiny.c b/kernel/rcu/tiny.c
>> index befc932..3345596 100644
>> --- a/kernel/rcu/tiny.c
>> +++ b/kernel/rcu/tiny.c
>> @@ -120,8 +120,10 @@ void rcu_bh_qs(void)
>>    */
>>   void rcu_check_callbacks(int user)
>>   {
>> -	if (user)
>> +	if (user) {
>>   		rcu_sched_qs();
>> +		rcu_tasks_qs();
>> +	}
>>   	if (user || !in_softirq())
>>   		rcu_bh_qs();
>>   }
>> -- 
>> 1.9.1
>>
> 
> 

-- 
Thanks,
Byungchul

      reply	other threads:[~2018-05-15  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  0:33 Byungchul Park
2018-05-15  4:11 ` Paul E. McKenney
2018-05-15  4:19   ` Byungchul Park [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=28cb032c-1c44-41b2-4703-e6f942d073de@lge.com \
    --to=byungchul.park@lge.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.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®