From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/5] ftrace: Updates for 6.14
Date: Tue, 24 Dec 2024 14:38:36 -0500 [thread overview]
Message-ID: <20241224193836.812390655@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ftrace/for-next
Head SHA1: d576aec24df9f58ed0ebe2ff854daafe837f0225
Masami Hiramatsu (Google) (1):
fgraph: Get ftrace recursion lock in function_graph_enter
Steven Rostedt (4):
fgraph: Remove unnecessary disabling of interrupts and recursion
ftrace: Do not disable interrupts in profiler
ftrace: Remove unneeded goto jumps
ftrace: Switch ftrace.c code over to use guard()
----
arch/powerpc/kernel/trace/ftrace.c | 6 --
arch/powerpc/kernel/trace/ftrace_64_pg.c | 6 --
arch/x86/kernel/ftrace.c | 7 --
kernel/trace/fgraph.c | 8 +-
kernel/trace/ftrace.c | 130 +++++++++++--------------------
kernel/trace/trace_functions_graph.c | 37 ++++-----
6 files changed, 67 insertions(+), 127 deletions(-)
next reply other threads:[~2024-12-24 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 19:38 Steven Rostedt [this message]
2024-12-24 19:38 ` [for-next][PATCH 1/5] fgraph: Remove unnecessary disabling of interrupts and recursion Steven Rostedt
2024-12-24 19:38 ` [for-next][PATCH 2/5] ftrace: Do not disable interrupts in profiler Steven Rostedt
2024-12-24 19:38 ` [for-next][PATCH 3/5] ftrace: Remove unneeded goto jumps Steven Rostedt
2024-12-24 19:38 ` [for-next][PATCH 4/5] ftrace: Switch ftrace.c code over to use guard() Steven Rostedt
2024-12-24 19:38 ` [for-next][PATCH 5/5] fgraph: Get ftrace recursion lock in function_graph_enter Steven Rostedt
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=20241224193836.812390655@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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 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®