From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Nicolas Saenz Julienne <nsaenzju@redhat.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
mtosatti@redhat.com, paulmck@kernel.org, rostedt@goodmis.org,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH] tracing/osnoise: Force quiescent states while tracing
Date: Fri, 4 Mar 2022 16:37:24 +0100 [thread overview]
Message-ID: <bc048c18-0ba7-1cb9-90a0-0bc049997c23@kernel.org> (raw)
In-Reply-To: <2b47679c6248a0d113b556ed6118e8ed72c74b29.camel@redhat.com>
On 3/4/22 16:28, Nicolas Saenz Julienne wrote:
> Some comments:
> - You're not exiting/entering EQS on IRQ/NMI entry/exit. See
> irqentry_{enter,exit}() and irqentry_nmi_{enter,exit}().
hummm, right!
> - See this series[1], if we ever pursue this approach, it's important we got
> through context tracking, instead of poking at RCU directly.
I had a test patch with context_tracking as well... entering and leaving using
it. Lemme find it.... but it basically works in the same way as for RCU (or
pretend to work).
>
> [1] https://lore.kernel.org/lkml/20220302154810.42308-1-frederic@kernel.org/T/#t
next prev parent reply other threads:[~2022-03-04 15:37 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
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 [this message]
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=bc048c18-0ba7-1cb9-90a0-0bc049997c23@kernel.org \
--to=bristot@kernel.org \
--cc=juri.lelli@redhat.com \
--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
Powered by JetHome