From: Menglong Dong <menglong8.dong@gmail.com>
To: mhiramat@kernel.org
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiang.biao@linux.dev, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] tracing: fprobe: optimization for entry only case
Date: Wed, 15 Oct 2025 16:32:36 +0800 [thread overview]
Message-ID: <20251015083238.2374294-1-dongml2@chinatelecom.cn> (raw)
The first patch is to optimize the fprobe for entry only case.
The second patch is to add testcase for mixed fprobe.
This series base on the "linux-trace" tree and "for-next" branch.
Changes since V3:
* fallback to fgraph if FTRACE_OPS_FL_SAVE_REGS not supported
Changes since V2:
* add some comment to the rcu_read_lock() in fprobe_ftrace_entry() in the
1st patch
Changes since V1:
* merge the rename of fprobe_entry into one
* add some document for fprobe_fgraph_entry as Masami suggested
* use ftrace_test_recursion_trylock() in fprobe_ftrace_entry()
* add the testcase for mixed fprobe
Menglong Dong (2):
tracing: fprobe: optimization for entry only case
lib/test_fprobe: add testcase for mixed fprobe
kernel/trace/fprobe.c | 127 ++++++++++++++++++++++++++++++++++++----
lib/tests/test_fprobe.c | 99 ++++++++++++++++++++++++++++++-
2 files changed, 214 insertions(+), 12 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-15 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 8:32 Menglong Dong [this message]
2025-10-15 8:32 ` [PATCH v4 1/2] " Menglong Dong
2025-10-22 22:52 ` Masami Hiramatsu
2025-10-15 8:32 ` [PATCH v4 2/2] lib/test_fprobe: add testcase for mixed fprobe Menglong Dong
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=20251015083238.2374294-1-dongml2@chinatelecom.cn \
--to=menglong8.dong@gmail.com \
--cc=jiang.biao@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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
all inboxes | Powered by JetHome®