From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/5] tracing: Various updates
Date: Mon, 29 Nov 2021 21:39:45 -0500 [thread overview]
Message-ID: <20211130023945.789683928@goodmis.org> (raw)
- Make trace_event_buffer_lock_reserver always disable preemption
(it says it does but not always)
- Have kprobes, uprobes and eprobes use
trace_event_buffer_lock_reserver() functions.
Steven Rostedt (VMware) (5):
tracing: Use __this_cpu_read() in trace_event_buffer_lock_reserver()
tracing: Disable preemption when using the filter buffer
tracing: Have eprobes use filtering logic of trace events
tracing/kprobes: Do not open code event reserve logic
tracing/uprobes: Use trace_event_buffer_reserve() helper
----
kernel/trace/trace.c | 59 +++++++++++++++++++++++++--------------------
kernel/trace/trace.h | 4 ++-
kernel/trace/trace_eprobe.c | 16 ++++--------
kernel/trace/trace_kprobe.c | 25 ++++++-------------
kernel/trace/trace_uprobe.c | 10 +++-----
5 files changed, 52 insertions(+), 62 deletions(-)
next reply other threads:[~2021-11-30 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 2:39 Steven Rostedt [this message]
2021-11-30 2:39 ` [PATCH 1/5] tracing: Use __this_cpu_read() in trace_event_buffer_lock_reserver() Steven Rostedt
2021-11-30 2:39 ` [PATCH 2/5] tracing: Disable preemption when using the filter buffer Steven Rostedt
2021-11-30 5:02 ` kernel test robot
2021-11-30 5:02 ` kernel test robot
2021-11-30 2:39 ` [PATCH 3/5] tracing: Have eprobes use filtering logic of trace events Steven Rostedt
2021-11-30 2:39 ` [PATCH 4/5] tracing/kprobes: Do not open code event reserve logic Steven Rostedt
2021-11-30 4:38 ` Masami Hiramatsu
2021-11-30 2:39 ` [PATCH 5/5] tracing/uprobes: Use trace_event_buffer_reserve() helper Steven Rostedt
2021-11-30 4:40 ` Masami Hiramatsu
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=20211130023945.789683928@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 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.