[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200319204838.1f78152a@gandalf.local.home>
Date: Thu, 19 Mar 2020 20:48:38 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, mingo@...nel.org, jiangshanlai@...il.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...icios.com, josh@...htriplett.org,
tglx@...utronix.de, peterz@...radead.org, dhowells@...hat.com,
edumazet@...gle.com, fweisbec@...il.com, oleg@...hat.com,
joel@...lfernandes.org,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Andrii Nakryiko <andriin@...com>
Subject: Re: [PATCH RFC v2 tip/core/rcu 14/22] rcu-tasks: Add an RCU Tasks
Trace to simplify protection of tracing hooks
On Thu, 19 Mar 2020 17:28:13 -0700
"Paul E. McKenney" <paulmck@...nel.org> wrote:
> Good point. If interrupts are disabled, it will need to use some
> other mechanism. One approach is irqwork. Another is a timer.
>
> Suggestions?
Ftrace and perf use irq_work, I would think that should work here too.
-- Steve
Powered by blists - more mailing lists