From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andriin@fb.com>
Subject: Re: [PATCH 6/8] ftrace: Add multi direct register/unregister interface
Date: Tue, 14 Sep 2021 17:35:55 -0400 [thread overview]
Message-ID: <20210914173555.056cd20c@oasis.local.home> (raw)
In-Reply-To: <20210831095017.412311-7-jolsa@kernel.org>
On Tue, 31 Aug 2021 11:50:15 +0200
Jiri Olsa <jolsa@redhat.com> wrote:
> Adding interface to register multiple direct functions
> within single call. Adding following functions:
>
> register_ftrace_direct_multi(struct ftrace_ops *ops, unsigned long addr)
> unregister_ftrace_direct_multi(struct ftrace_ops *ops)
>
> The register_ftrace_direct_multi registers direct function (addr)
> with all functions in ops filter. The ops filter can be updated
> before with ftrace_set_filter_ip calls.
>
> All requested functions must not have direct function currently
> registered, otherwise register_ftrace_direct_multi will fail.
>
> The unregister_ftrace_direct_multi unregisters ops related direct
> functions.
>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> include/linux/ftrace.h | 11 ++++
> kernel/trace/ftrace.c | 111 +++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 122 insertions(+)
>
> diff --git a/include/linux/ftrace.h b/include/linux/ftrace.h
> index d399621a67ee..e40b5201c16e 100644
> --- a/include/linux/ftrace.h
> +++ b/include/linux/ftrace.h
> @@ -316,7 +316,10 @@ int ftrace_modify_direct_caller(struct ftrace_func_entry *entry,
> unsigned long old_addr,
> unsigned long new_addr);
> unsigned long ftrace_find_rec_direct(unsigned long ip);
> +int register_ftrace_direct_multi(struct ftrace_ops *ops, unsigned long addr);
> +int unregister_ftrace_direct_multi(struct ftrace_ops *ops);
> #else
> +struct ftrace_ops;
> # define ftrace_direct_func_count 0
> static inline int register_ftrace_direct(unsigned long ip, unsigned long addr)
> {
> @@ -346,6 +349,14 @@ static inline unsigned long ftrace_find_rec_direct(unsigned long ip)
> {
> return 0;
> }
> +static inline int register_ftrace_direct_multi(struct ftrace_ops *ops, unsigned long addr)
> +{
> + return -ENODEV;
> +}
> +static inline int unregister_ftrace_direct_multi(struct ftrace_ops *ops)
> +{
> + return -ENODEV;
> +}
> #endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */
>
> #ifndef CONFIG_HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index c60217d81040..7243769493c9 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -5407,6 +5407,117 @@ int modify_ftrace_direct(unsigned long ip,
> return ret;
> }
> EXPORT_SYMBOL_GPL(modify_ftrace_direct);
> +
> +#define MULTI_FLAGS (FTRACE_OPS_FL_IPMODIFY | FTRACE_OPS_FL_DIRECT | \
> + FTRACE_OPS_FL_SAVE_REGS)
> +
> +static int check_direct_multi(struct ftrace_ops *ops)
> +{
> + if (!(ops->flags & FTRACE_OPS_FL_INITIALIZED))
> + return -EINVAL;
> + if ((ops->flags & MULTI_FLAGS) != MULTI_FLAGS)
> + return -EINVAL;
> + return 0;
> +}
> +
Needs kernel doc comments as this is an interface outside this file.
> +int register_ftrace_direct_multi(struct ftrace_ops *ops, unsigned long addr)
> +{
> + struct ftrace_hash *hash, *free_hash = NULL;
> + struct ftrace_func_entry *entry, *new;
> + int err = -EBUSY, size, i;
> +
> + if (ops->func || ops->trampoline)
> + return -EINVAL;
> + if (!(ops->flags & FTRACE_OPS_FL_INITIALIZED))
> + return -EINVAL;
> + if (ops->flags & FTRACE_OPS_FL_ENABLED)
> + return -EINVAL;
> +
> + hash = ops->func_hash->filter_hash;
> + if (ftrace_hash_empty(hash))
> + return -EINVAL;
> +
> + mutex_lock(&direct_mutex);
> +
> + /* Make sure requested entries are not already registered.. */
> + size = 1 << hash->size_bits;
> + for (i = 0; i < size; i++) {
> + hlist_for_each_entry(entry, &hash->buckets[i], hlist) {
> + if (ftrace_find_rec_direct(entry->ip))
> + goto out_unlock;
> + }
> + }
> +
> + /* ... and insert them to direct_functions hash. */
> + err = -ENOMEM;
> + for (i = 0; i < size; i++) {
> + hlist_for_each_entry(entry, &hash->buckets[i], hlist) {
> + new = ftrace_add_rec_direct(entry->ip, addr, &free_hash);
> + if (!new)
> + goto out_remove;
> + entry->direct = addr;
> + }
> + }
> +
> + ops->func = call_direct_funcs;
> + ops->flags = MULTI_FLAGS;
> + ops->trampoline = FTRACE_REGS_ADDR;
> +
> + err = register_ftrace_function(ops);
> +
> + out_remove:
> + if (err) {
The below code:
> + for (i = 0; i < size; i++) {
> + hlist_for_each_entry(entry, &hash->buckets[i], hlist) {
> + new = __ftrace_lookup_ip(direct_functions, entry->ip);
> + if (new) {
> + remove_hash_entry(direct_functions, new);
> + kfree(new);
> + }
> + }
> + }
is identical to code below.
> + }
> +
> + out_unlock:
> + mutex_unlock(&direct_mutex);
> +
> + if (free_hash) {
> + synchronize_rcu_tasks();
> + free_ftrace_hash(free_hash);
> + }
> + return err;
> +}
> +EXPORT_SYMBOL_GPL(register_ftrace_direct_multi);
> +
Should have kernel doc as well.
> +int unregister_ftrace_direct_multi(struct ftrace_ops *ops)
> +{
> + struct ftrace_hash *hash = ops->func_hash->filter_hash;
> + struct ftrace_func_entry *entry, *new;
> + int err, size, i;
> +
> + if (check_direct_multi(ops))
> + return -EINVAL;
> + if (!(ops->flags & FTRACE_OPS_FL_ENABLED))
> + return -EINVAL;
> +
> + mutex_lock(&direct_mutex);
> + err = unregister_ftrace_function(ops);
> +
> + size = 1 << hash->size_bits;
> + for (i = 0; i < size; i++) {
> + hlist_for_each_entry(entry, &hash->buckets[i], hlist) {
> + new = __ftrace_lookup_ip(direct_functions, entry->ip);
> + if (new) {
> + remove_hash_entry(direct_functions, new);
> + kfree(new);
> + }
> + }
> + }
Would probably make sense to turn this into a static inline helper.
-- Steve
> +
> + mutex_unlock(&direct_mutex);
> + return err;
> +}
> +EXPORT_SYMBOL_GPL(unregister_ftrace_direct_multi);
> #endif /* CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS */
>
> /**
next prev parent reply other threads:[~2021-09-14 21:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 9:50 [PATCH 0/8] x86/ftrace: Add direct batch interface Jiri Olsa
2021-08-31 9:50 ` [PATCH 1/8] x86/ftrace: Remove extra orig rax move Jiri Olsa
2021-08-31 9:50 ` [PATCH 2/8] x86/ftrace: Remove fault protection code in prepare_ftrace_return Jiri Olsa
2021-08-31 9:50 ` [PATCH 3/8] x86/ftrace: Make function graph use ftrace directly Jiri Olsa
2021-08-31 9:50 ` [PATCH 4/8] tracing: Add trampoline/graph selftest Jiri Olsa
2021-08-31 9:50 ` [PATCH 5/8] ftrace: Add ftrace_add_rec_direct function Jiri Olsa
2021-08-31 9:50 ` [PATCH 6/8] ftrace: Add multi direct register/unregister interface Jiri Olsa
2021-09-14 21:35 ` Steven Rostedt [this message]
2021-09-16 19:45 ` Jiri Olsa
2021-08-31 9:50 ` [PATCH 7/8] ftrace: Add multi direct modify interface Jiri Olsa
2021-09-14 21:41 ` Steven Rostedt
2021-09-15 21:47 ` Steven Rostedt
2021-09-16 19:49 ` Jiri Olsa
2021-09-16 20:41 ` Steven Rostedt
2021-08-31 9:50 ` [PATCH 8/8] ftrace/samples: Add multi direct interface test module Jiri Olsa
2021-09-01 15:23 ` [PATCH 0/8] x86/ftrace: Add direct batch interface Alexei Starovoitov
2021-09-01 19:06 ` Jiri Olsa
2021-09-02 14:54 ` Steven Rostedt
2021-10-08 9:13 [PATCHv2 " Jiri Olsa
2021-10-08 9:13 ` [PATCH 6/8] ftrace: Add multi direct register/unregister interface Jiri Olsa
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=20210914173555.056cd20c@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).