From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: paulmck@kernel.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
Nicolas Saenz Julienne <nsaenzju@redhat.com>
Subject: Re: [PATCH] tracing/osnoise: Force quiescent states while tracing
Date: Tue, 1 Mar 2022 18:30:07 +0100 [thread overview]
Message-ID: <a4fa8045-64f9-5550-7f03-b6819aeeb6c4@kernel.org> (raw)
In-Reply-To: <6bd3b0083427c6cf1c860a021e097af9052cdd75.camel@redhat.com>
On 3/1/22 11:59, Nicolas Saenz Julienne wrote:
>> I wonder if this is similar to what we have in trace_benchmark(). Would
>> using: cond_resched_tasks_rcu_qs() work for you?
> IIUC this only affects tasks_rcu, and doesn't help with regular RCU. We already
> call cond_resched_tasks_rcu_qs() in osnoise when necesary, actually it was
> introduced by you. :)
I tried using cond_resched_tasks_rcu_qs() to solve the same problem before, it
did not work.
-- Daniel
next prev parent reply other threads:[~2022-03-01 17:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:14 Nicolas Saenz Julienne
2022-02-28 15:45 ` Steven Rostedt
2022-03-01 10:59 ` Nicolas Saenz Julienne
2022-03-01 17:30 ` Daniel Bristot de Oliveira [this message]
2022-02-28 20:00 ` Daniel Bristot de Oliveira
2022-03-01 10:52 ` Nicolas Saenz Julienne
2022-03-01 17:55 ` Daniel Bristot de Oliveira
2022-03-01 18:05 ` Paul E. McKenney
2022-03-01 18:44 ` Daniel Bristot de Oliveira
2022-03-01 18:58 ` Paul E. McKenney
2022-03-01 19:29 ` Daniel Bristot de Oliveira
2022-03-01 19:46 ` Paul E. McKenney
2022-03-01 19:53 ` Daniel Bristot de Oliveira
2022-02-28 22:11 ` Paul E. McKenney
2022-03-01 10:00 ` Nicolas Saenz Julienne
2022-03-01 17:44 ` Daniel Bristot de Oliveira
2022-03-01 17:56 ` Paul E. McKenney
2022-03-02 10:46 ` Nicolas Saenz Julienne
2022-03-04 14:28 ` Daniel Bristot de Oliveira
2022-03-04 14:36 ` Nicolas Saenz Julienne
2022-03-04 14:39 ` Daniel Bristot de Oliveira
2022-03-04 14:51 ` Daniel Bristot de Oliveira
2022-03-04 15:28 ` Nicolas Saenz Julienne
2022-03-04 15:37 ` Daniel Bristot de Oliveira
2022-03-04 15:55 ` Nicolas Saenz Julienne
2022-03-04 16:26 ` Paul E. McKenney
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=a4fa8045-64f9-5550-7f03-b6819aeeb6c4@kernel.org \
--to=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=paulmck@kernel.org \
--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®