From: Steven Rostedt <rostedt@goodmis.org>
To: Naveen N Rao <naveen@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [RFC PATCH v2 2/5] powerpc/ftrace: Remove pointer to struct module from dyn_arch_ftrace
Date: Mon, 10 Jun 2024 16:03:56 -0400 [thread overview]
Message-ID: <20240610160356.70e8f7ac@gandalf.local.home> (raw)
In-Reply-To: <50b038f167f3fb94ed6074e029b6794bbe6e83a2.1718008093.git.naveen@kernel.org>
On Mon, 10 Jun 2024 14:08:15 +0530
Naveen N Rao <naveen@kernel.org> wrote:
> Pointer to struct module is only relevant for ftrace records belonging
> to kernel modules. Having this field in dyn_arch_ftrace wastes memory
> for all ftrace records belonging to the kernel. Remove the same in
> favour of looking up the module from the ftrace record address, similar
> to other architectures.
>
> Signed-off-by: Naveen N Rao <naveen@kernel.org>
> ---
> arch/powerpc/include/asm/ftrace.h | 1 -
> arch/powerpc/kernel/trace/ftrace.c | 47 ++++++++++-----
> arch/powerpc/kernel/trace/ftrace_64_pg.c | 73 +++++++++++-------------
> 3 files changed, 64 insertions(+), 57 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/ftrace.h b/arch/powerpc/include/asm/ftrace.h
> index 107fc5a48456..201f9d15430a 100644
> --- a/arch/powerpc/include/asm/ftrace.h
> +++ b/arch/powerpc/include/asm/ftrace.h
> @@ -26,7 +26,6 @@ unsigned long prepare_ftrace_return(unsigned long parent, unsigned long ip,
> struct module;
> struct dyn_ftrace;
> struct dyn_arch_ftrace {
> - struct module *mod;
> };
Nice. I always hated that extra field.
>
> #ifdef CONFIG_DYNAMIC_FTRACE_WITH_ARGS
> diff --git a/arch/powerpc/kernel/trace/ftrace.c b/arch/powerpc/kernel/trace/ftrace.c
> index d8d6b4fd9a14..041be965485e 100644
> --- a/arch/powerpc/kernel/trace/ftrace.c
> +++ b/arch/powerpc/kernel/trace/ftrace.c
> @@ -106,20 +106,36 @@ static unsigned long find_ftrace_tramp(unsigned long ip)
> return 0;
> }
>
> +static struct module *ftrace_lookup_module(struct dyn_ftrace *rec)
> +{
> + struct module *mod = NULL;
> +
> +#ifdef CONFIG_MODULES
> + /*
> + * NOTE: __module_text_address() must be called with preemption
> + * disabled, but we can rely on ftrace_lock to ensure that 'mod'
> + * retains its validity throughout the remainder of this code.
> + */
> + preempt_disable();
> + mod = __module_text_address(rec->ip);
> + preempt_enable();
> +
> + if (!mod)
> + pr_err("No module loaded at addr=%lx\n", rec->ip);
> +#endif
> +
> + return mod;
> +}
It may look nicer to have:
#ifdef CONFIG_MODULES
static struct module *ftrace_lookup_module(struct dyn_ftrace *rec)
{
struct module *mod = NULL;
/*
* NOTE: __module_text_address() must be called with preemption
* disabled, but we can rely on ftrace_lock to ensure that 'mod'
* retains its validity throughout the remainder of this code.
*/
preempt_disable();
mod = __module_text_address(rec->ip);
preempt_enable();
if (!mod)
pr_err("No module loaded at addr=%lx\n", rec->ip);
return mod;
}
#else
static inline struct module *ftrace_lookup_module(struct dyn_ftrace *rec)
{
return NULL;
}
#endif
> +
> static int ftrace_get_call_inst(struct dyn_ftrace *rec, unsigned long addr, ppc_inst_t *call_inst)
> {
> unsigned long ip = rec->ip;
> unsigned long stub;
> + struct module *mod;
>
> if (is_offset_in_branch_range(addr - ip)) {
> /* Within range */
> stub = addr;
> -#ifdef CONFIG_MODULES
> - } else if (rec->arch.mod) {
> - /* Module code would be going to one of the module stubs */
> - stub = (addr == (unsigned long)ftrace_caller ? rec->arch.mod->arch.tramp :
> - rec->arch.mod->arch.tramp_regs);
> -#endif
> } else if (core_kernel_text(ip)) {
> /* We would be branching to one of our ftrace stubs */
> stub = find_ftrace_tramp(ip);
> @@ -128,7 +144,16 @@ static int ftrace_get_call_inst(struct dyn_ftrace *rec, unsigned long addr, ppc_
> return -EINVAL;
> }
> } else {
> - return -EINVAL;
> + mod = ftrace_lookup_module(rec);
> + if (mod) {
> +#ifdef CONFIG_MODULES
> + /* Module code would be going to one of the module stubs */
> + stub = (addr == (unsigned long)ftrace_caller ? mod->arch.tramp :
> + mod->arch.tramp_regs);
> +#endif
You have CONFIG_MODULES here and in ftrace_lookup_module() above, which
would always return NULL. Could you combine the above to be done in
ftrace_lookup_module() so that there's no #ifdef CONFIG_MODULES here?
> + } else {
> + return -EINVAL;
> + }
> }
>
> *call_inst = ftrace_create_branch_inst(ip, stub, 1);
> @@ -256,14 +281,6 @@ int ftrace_init_nop(struct module *mod, struct dyn_ftrace *rec)
> if (ret)
> return ret;
>
> - if (!core_kernel_text(ip)) {
> - if (!mod) {
> - pr_err("0x%lx: No module provided for non-kernel address\n", ip);
> - return -EFAULT;
> - }
> - rec->arch.mod = mod;
> - }
> -
> /* Nop-out the ftrace location */
> new = ppc_inst(PPC_RAW_NOP());
> addr = MCOUNT_ADDR;
-- Steve
next prev parent reply other threads:[~2024-06-10 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 8:38 [RFC PATCH v2 0/5] powerpc/ftrace: Move ftrace sequence out of line Naveen N Rao
2024-06-10 8:38 ` [RFC PATCH v2 1/5] powerpc/kprobes: Use ftrace to determine if a probe is at function entry Naveen N Rao
2024-06-10 8:38 ` [RFC PATCH v2 2/5] powerpc/ftrace: Remove pointer to struct module from dyn_arch_ftrace Naveen N Rao
2024-06-10 20:03 ` Steven Rostedt [this message]
2024-06-11 14:45 ` Naveen N Rao
2024-06-10 8:38 ` [RFC PATCH v2 3/5] powerpc/ftrace: Unify 32-bit and 64-bit ftrace entry code Naveen N Rao
2024-06-10 20:06 ` Steven Rostedt
2024-06-11 14:47 ` Naveen N Rao
2024-06-11 15:14 ` Steven Rostedt
2024-06-10 8:38 ` [RFC PATCH v2 4/5] kbuild: Add generic hook for architectures to use before the final vmlinux link Naveen N Rao
2024-06-10 9:14 ` Masahiro Yamada
2024-06-10 17:16 ` Naveen N Rao
2024-06-10 21:51 ` Masahiro Yamada
2024-06-11 17:35 ` Naveen N Rao
2024-06-12 10:52 ` Naveen N Rao
2024-06-10 8:38 ` [RFC PATCH v2 5/5] powerpc64/ftrace: Move ftrace sequence out of line Naveen N Rao
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=20240610160356.70e8f7ac@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
/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).