public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Florent Revest <revest@chromium.org>,
	linux-trace-kernel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Alan Maguire <alan.maguire@oracle.com>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH v20 00/19] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph
Date: Mon, 9 Dec 2024 15:36:51 +0900	[thread overview]
Message-ID: <20241209153651.c622af218b5d4b2c2da76158@kernel.org> (raw)
In-Reply-To: <20241207094710.21cdaceb@rorschach.local.home>

On Sat, 7 Dec 2024 09:47:10 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Sat, 7 Dec 2024 15:51:36 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> 
> > This checks the handler is called with preempt off.
> > 
> > On x86_64, the ftrace_graph_func calls function_graph_enter_regs() with
> > ftrace_test_recursion_trylock() as below;
> > 
> > void ftrace_graph_func(unsigned long ip, unsigned long parent_ip,
> > 		       struct ftrace_ops *op, struct ftrace_regs *fregs)
> > {
> > 	struct pt_regs *regs = &arch_ftrace_regs(fregs)->regs;
> > 	unsigned long *stack = (unsigned long *)kernel_stack_pointer(regs);
> > 	unsigned long return_hooker = (unsigned long)&return_to_handler;
> > 	unsigned long *parent = (unsigned long *)stack;
> > 	int bit;
> > 
> > 	if (unlikely(skip_ftrace_return()))
> > 		return;
> > 
> > 	bit = ftrace_test_recursion_trylock(ip, *parent);
> > 	if (bit < 0)
> > 		return;
> > 
> > 	if (!function_graph_enter_regs(*parent, ip, 0, parent, fregs))
> > 		*parent = return_hooker;
> > 
> > 	ftrace_test_recursion_unlock(bit);
> > }
> > 
> > However, arm64 version does not;
> 
> Hmm, I think we can move that recursion check out of the arch/x86 code
> and into ftrace_graph_enter_regs().

OK, that's reasonable.

Thanks,

> 
> -- Steve


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2024-12-09  6:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  0:08 [PATCH v20 00/19] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph Masami Hiramatsu (Google)
2024-12-06  0:09 ` [PATCH v20 01/19] fgraph: Pass ftrace_regs to entryfunc Masami Hiramatsu (Google)
2024-12-06  0:09 ` [PATCH v20 02/19] fgraph: Replace fgraph_ret_regs with ftrace_regs Masami Hiramatsu (Google)
2024-12-06  0:09 ` [PATCH v20 03/19] fgraph: Pass ftrace_regs to retfunc Masami Hiramatsu (Google)
2024-12-06  0:09 ` [PATCH v20 04/19] fprobe: Use ftrace_regs in fprobe entry handler Masami Hiramatsu (Google)
2024-12-06  0:09 ` [PATCH v20 05/19] fprobe: Use ftrace_regs in fprobe exit handler Masami Hiramatsu (Google)
2024-12-06  0:10 ` [PATCH v20 06/19] tracing: Add ftrace_partial_regs() for converting ftrace_regs to pt_regs Masami Hiramatsu (Google)
2024-12-06  0:10 ` [PATCH v20 07/19] tracing: Add ftrace_fill_perf_regs() for perf event Masami Hiramatsu (Google)
2024-12-06  0:10 ` [PATCH v20 08/19] tracing/fprobe: Enable fprobe events with CONFIG_DYNAMIC_FTRACE_WITH_ARGS Masami Hiramatsu (Google)
2024-12-06  0:10 ` [PATCH v20 09/19] bpf: Enable kprobe_multi feature if CONFIG_FPROBE is enabled Masami Hiramatsu (Google)
2024-12-06  0:11 ` [PATCH v20 10/19] ftrace: Add CONFIG_HAVE_FTRACE_GRAPH_FUNC Masami Hiramatsu (Google)
2024-12-06  0:11 ` [PATCH v20 11/19] s390/tracing: Enable HAVE_FTRACE_GRAPH_FUNC Masami Hiramatsu (Google)
2024-12-06  0:11 ` [PATCH v20 12/19] fprobe: Rewrite fprobe on function-graph tracer Masami Hiramatsu (Google)
2024-12-06  0:11 ` [PATCH v20 13/19] fprobe: Add fprobe_header encoding feature Masami Hiramatsu (Google)
2024-12-06  0:11 ` [PATCH v20 14/19] tracing/fprobe: Remove nr_maxactive from fprobe Masami Hiramatsu (Google)
2024-12-06  0:12 ` [PATCH v20 15/19] selftests: ftrace: Remove obsolate maxactive syntax check Masami Hiramatsu (Google)
2024-12-06  0:12 ` [PATCH v20 16/19] selftests/ftrace: Add a test case for repeating register/unregister fprobe Masami Hiramatsu (Google)
2024-12-06  0:12 ` [PATCH v20 17/19] Documentation: probes: Update fprobe on function-graph tracer Masami Hiramatsu (Google)
2024-12-06  0:12 ` [PATCH v20 18/19] ftrace: Add ftrace_get_symaddr to convert fentry_ip to symaddr Masami Hiramatsu (Google)
2024-12-06  0:12 ` [PATCH v20 19/19] bpf: Use ftrace_get_symaddr() in get_entry_ip() Masami Hiramatsu (Google)
2024-12-06  8:20 ` [PATCH v20 00/19] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph Masami Hiramatsu
2024-12-07  6:51   ` Masami Hiramatsu
2024-12-07 14:47     ` Steven Rostedt
2024-12-09  6:36       ` Masami Hiramatsu [this message]
2024-12-06  9:35 ` Heiko Carstens
2024-12-06 14:52   ` Steven Rostedt
2024-12-09  6:36     ` 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=20241209153651.c622af218b5d4b2c2da76158@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.lau@linux.dev \
    --cc=revest@chromium.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