From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Florent Revest <revest@chromium.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhiramat@kernel.org, mark.rutland@arm.com, ast@kernel.org,
daniel@iogearbox.net, kpsingh@kernel.org
Subject: Re: [PATCH 4/7] ftrace: Rename _ftrace_direct_multi APIs to _ftrace_direct APIs
Date: Sun, 19 Mar 2023 13:55:50 -0400 [thread overview]
Message-ID: <20230319135550.22aaa04b@rorschach.local.home> (raw)
In-Reply-To: <ZBcqWqWyq0uW/wj7@krava>
On Sun, 19 Mar 2023 16:29:30 +0100
Jiri Olsa <olsajiri@gmail.com> wrote:
> On Thu, Mar 16, 2023 at 06:38:08PM +0100, Florent Revest wrote:
>
> SNIP
>
> > diff --git a/samples/Kconfig b/samples/Kconfig
> > index 30ef8bd48ba3..fd24daa99f34 100644
> > --- a/samples/Kconfig
> > +++ b/samples/Kconfig
> > @@ -38,7 +38,7 @@ config SAMPLE_FTRACE_DIRECT
> > that hooks to wake_up_process and prints the parameters.
> >
> > config SAMPLE_FTRACE_DIRECT_MULTI
>
> nit, we could perhaps remove this config option as well
> and use SAMPLE_FTRACE_DIRECT_MULTI
Remove SAMPLE_FTRACE_DIRECT_MULTI for SAMPLE_FTRACE_DIRECT_MULTI?
-- Steve
>
> jirka
>
> > - tristate "Build register_ftrace_direct_multi() example"
> > + tristate "Build register_ftrace_direct() on multiple ips example"
> > depends on DYNAMIC_FTRACE_WITH_DIRECT_CALLS && m
> > depends on HAVE_SAMPLE_FTRACE_DIRECT_MULTI
> > help
next prev parent reply other threads:[~2023-03-19 17:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 17:38 [PATCH 0/7] Refactor ftrace direct call APIs Florent Revest
2023-03-16 17:38 ` [PATCH 1/7] ftrace: Let unregister_ftrace_direct_multi() call ftrace_free_filter() Florent Revest
2023-03-21 9:47 ` Mark Rutland
2023-03-21 10:40 ` Jiri Olsa
2023-03-16 17:38 ` [PATCH 2/7] ftrace: Replace uses of _ftrace_direct APIs with _ftrace_direct_multi Florent Revest
2023-03-16 17:38 ` [PATCH 3/7] ftrace: Remove the legacy _ftrace_direct API Florent Revest
2023-03-16 17:38 ` [PATCH 4/7] ftrace: Rename _ftrace_direct_multi APIs to _ftrace_direct APIs Florent Revest
2023-03-19 15:29 ` Jiri Olsa
2023-03-19 17:55 ` Steven Rostedt [this message]
2023-03-19 18:22 ` Jiri Olsa
2023-03-20 0:47 ` Steven Rostedt
2023-03-20 8:05 ` Jiri Olsa
2023-03-20 17:41 ` Florent Revest
2023-03-16 17:38 ` [PATCH 5/7] ftrace: Store direct called addresses in their ops Florent Revest
2023-03-19 15:29 ` Jiri Olsa
2023-03-19 17:54 ` Steven Rostedt
2023-03-19 18:54 ` Jiri Olsa
2023-03-20 17:45 ` Florent Revest
2023-03-20 21:31 ` Steven Rostedt
2023-03-21 10:20 ` Mark Rutland
2023-03-16 17:38 ` [PATCH 6/7] ftrace: Make DIRECT_CALLS work WITH_ARGS and !WITH_REGS Florent Revest
2023-03-16 17:38 ` [PATCH 7/7] ftrace: selftest: remove broken trace_direct_tramp Florent Revest
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=20230319135550.22aaa04b@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=olsajiri@gmail.com \
--cc=revest@chromium.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.