From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Joel Fernandes <joelaf@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Boqun Feng <boqun.feng@gmail.com>, fweisbec <fweisbec@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
kbuild test robot <fengguang.wu@intel.com>,
baohong liu <baohong.liu@intel.com>,
vedang patel <vedang.patel@intel.com>,
kernel-team <kernel-team@android.com>
Subject: Re: [PATCH RFC] tracepoint: Introduce tracepoint callbacks executing with preempt on
Date: Fri, 27 Apr 2018 12:08:58 -0400 [thread overview]
Message-ID: <20180427120858.1357f1e0@gandalf.local.home> (raw)
In-Reply-To: <1953337577.5844.1524843821731.JavaMail.zimbra@efficios.com>
On Fri, 27 Apr 2018 11:43:41 -0400 (EDT)
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> It does so by disabling preemption in the callbacks, even when it's
> redundant with the guarantees already provided by tracepoint-sched-rcu
> and by kprobes. It's not that great for a fast-path.
Really, preempt_disable() is not bad for a fast path. It's far better
than a local_irq_disable().
-- Steve
next prev parent reply other threads:[~2018-04-27 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 4:26 [PATCH RFC] tracepoint: Introduce tracepoint callbacks executing with preempt on Joel Fernandes
2018-04-27 14:26 ` Mathieu Desnoyers
2018-04-27 14:47 ` Steven Rostedt
2018-04-27 15:38 ` Paul E. McKenney
2018-04-27 15:40 ` Steven Rostedt
2018-04-27 15:43 ` Mathieu Desnoyers
2018-04-27 16:08 ` Steven Rostedt [this message]
2018-04-27 15:58 ` Paul E. McKenney
2018-04-27 15:42 ` Mathieu Desnoyers
2018-04-27 16:07 ` Steven Rostedt
2018-04-27 16:30 ` Joel Fernandes
2018-04-27 16:37 ` Steven Rostedt
2018-04-27 18:11 ` Joel Fernandes
2018-04-27 18:42 ` Mathieu Desnoyers
2018-04-27 15:57 ` Paul E. McKenney
2018-04-27 16:13 ` Steven Rostedt
2018-04-27 16:22 ` Joel Fernandes
2018-04-27 16:44 ` Paul E. McKenney
2018-04-27 16:14 ` Joel Fernandes
2018-04-27 16:22 ` Steven Rostedt
2018-04-27 16:45 ` Paul E. McKenney
2018-04-27 16:46 ` Steven Rostedt
2018-04-27 17:00 ` Paul E. McKenney
2018-04-27 17:05 ` 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=20180427120858.1357f1e0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=baohong.liu@intel.com \
--cc=boqun.feng@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=vedang.patel@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.