From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org,
Michael Jeanson <mjeanson@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>, Yonghong Song <yhs@fb.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
bpf@vger.kernel.org, Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [RFC PATCH v3 1/5] tracing: Introduce faultable tracepoints (v3)
Date: Tue, 3 Oct 2023 10:08:54 -0400 [thread overview]
Message-ID: <20231003100854.7285d2a9@gandalf.local.home> (raw)
In-Reply-To: <5d0771e9-332c-42cd-acf3-53d46bb691f3@paulmck-laptop>
On Tue, 3 Oct 2023 06:44:50 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> > That way it is clear what uses what, as I read the original paragraph a
> > couple of times and could have sworn that rcu_read_lock_trace() required
> > tasks to not block.
>
> That would work for me. Would you like to send a patch, or would you
> rather we made the adjustments?
Which ever.
-- Steve
next prev parent reply other threads:[~2023-10-03 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 20:25 [RFC PATCH v3 0/5] Faultable Tracepoints Mathieu Desnoyers
2023-10-02 20:25 ` [RFC PATCH v3 1/5] tracing: Introduce faultable tracepoints (v3) Mathieu Desnoyers
2023-10-02 23:10 ` Steven Rostedt
2023-10-03 0:14 ` Paul E. McKenney
2023-10-03 1:19 ` Steven Rostedt
2023-10-03 13:44 ` Paul E. McKenney
2023-10-03 14:08 ` Steven Rostedt [this message]
2023-10-03 17:33 ` Paul E. McKenney
2023-10-03 17:37 ` Mathieu Desnoyers
2023-10-03 17:38 ` Steven Rostedt
2023-10-03 18:15 ` Paul E. McKenney
2023-10-02 20:25 ` [RFC PATCH v3 2/5] tracing/ftrace: Add support for faultable tracepoints Mathieu Desnoyers
2023-10-02 20:25 ` [RFC PATCH v3 3/5] tracing/bpf-trace: add " Mathieu Desnoyers
2023-10-02 20:25 ` [RFC PATCH v3 4/5] tracing/perf: " Mathieu Desnoyers
2023-10-02 20:25 ` [RFC PATCH v3 5/5] tracing: convert sys_enter/exit to " Mathieu Desnoyers
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=20231003100854.7285d2a9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=mjeanson@efficios.com \
--cc=namhyung@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=yhs@fb.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 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®