linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Naveen N Rao <naveen@kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 13/17] powerpc/ftrace: Simplify ftrace_modify_call()
Date: Fri, 23 Jun 2023 05:31:19 +0000	[thread overview]
Message-ID: <5011fa7e-a228-9ef2-2dff-9ca1931df26f@csgroup.eu> (raw)
In-Reply-To: <06275720939f8ee4c2f61c9e9a3e89b1fa3c441d.1687166935.git.naveen@kernel.org>



Le 19/06/2023 à 11:47, Naveen N Rao a écrit :
> Now that we validate the ftrace location during initialization in
> ftrace_init_nop(), we can simplify ftrace_modify_call() to patch-in the
> updated branch instruction without worrying about the instructions
> surrounding the ftrace location. Note that we continue to ensure we
> have the expected branch instruction at the ftrace location before
> patching it with the updated branch destination.
> 
> Signed-off-by: Naveen N Rao <naveen@kernel.org>

Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>

> ---
>   arch/powerpc/kernel/trace/ftrace.c | 161 ++++-------------------------
>   1 file changed, 21 insertions(+), 140 deletions(-)
> 
> diff --git a/arch/powerpc/kernel/trace/ftrace.c b/arch/powerpc/kernel/trace/ftrace.c
> index 6ea8b90246a540..c37e22c6c26521 100644
> --- a/arch/powerpc/kernel/trace/ftrace.c
> +++ b/arch/powerpc/kernel/trace/ftrace.c
> @@ -89,33 +89,11 @@ static inline int ftrace_modify_code(unsigned long ip, ppc_inst_t old, ppc_inst_
>   	return ret;
>   }
>   
> -/*
> - * Helper functions that are the same for both PPC64 and PPC32.
> - */
> -static int test_24bit_addr(unsigned long ip, unsigned long addr)
> -{
> -	addr = ppc_function_entry((void *)addr);
> -
> -	return is_offset_in_branch_range(addr - ip);
> -}
> -
>   static int is_bl_op(ppc_inst_t op)
>   {
>   	return (ppc_inst_val(op) & ~PPC_LI_MASK) == PPC_RAW_BL(0);
>   }
>   
> -static unsigned long find_bl_target(unsigned long ip, ppc_inst_t op)
> -{
> -	int offset;
> -
> -	offset = PPC_LI(ppc_inst_val(op));
> -	/* make it signed */
> -	if (offset & 0x02000000)
> -		offset |= 0xfe000000;
> -
> -	return ip + (long)offset;
> -}
> -
>   static unsigned long find_ftrace_tramp(unsigned long ip)
>   {
>   	int i;
> @@ -130,115 +108,16 @@ static unsigned long find_ftrace_tramp(unsigned long ip)
>   }
>   
>   #ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS
> -#ifdef CONFIG_MODULES
> -static int
> -__ftrace_modify_call(struct dyn_ftrace *rec, unsigned long old_addr,
> -					unsigned long addr)
> +int ftrace_modify_call(struct dyn_ftrace *rec, unsigned long old_addr, unsigned long addr)
>   {
> -	ppc_inst_t op;
> -	unsigned long ip = rec->ip;
> -	unsigned long entry, ptr, tramp;
> -	struct module *mod = rec->arch.mod;
> -
> -	/* If we never set up ftrace trampolines, then bail */
> -	if (!mod->arch.tramp || !mod->arch.tramp_regs) {
> -		pr_err("No ftrace trampoline\n");
> -		return -EINVAL;
> -	}
> -
> -	/* read where this goes */
> -	if (copy_inst_from_kernel_nofault(&op, (void *)ip)) {
> -		pr_err("Fetching opcode failed.\n");
> -		return -EFAULT;
> -	}
> -
> -	/* Make sure that this is still a 24bit jump */
> -	if (!is_bl_op(op)) {
> -		pr_err("Not expected bl: opcode is %08lx\n", ppc_inst_as_ulong(op));
> -		return -EINVAL;
> -	}
> -
> -	/* lets find where the pointer goes */
> -	tramp = find_bl_target(ip, op);
> -	entry = ppc_global_function_entry((void *)old_addr);
> -
> -	pr_devel("ip:%lx jumps to %lx", ip, tramp);
> -
> -	if (tramp != entry) {
> -		/* old_addr is not within range, so we must have used a trampoline */
> -		if (module_trampoline_target(mod, tramp, &ptr)) {
> -			pr_err("Failed to get trampoline target\n");
> -			return -EFAULT;
> -		}
> -
> -		pr_devel("trampoline target %lx", ptr);
> -
> -		/* This should match what was called */
> -		if (ptr != entry) {
> -			pr_err("addr %lx does not match expected %lx\n", ptr, entry);
> -			return -EINVAL;
> -		}
> -	}
> -
> -	/* The new target may be within range */
> -	if (test_24bit_addr(ip, addr)) {
> -		/* within range */
> -		if (patch_branch((u32 *)ip, addr, BRANCH_SET_LINK)) {
> -			pr_err("REL24 out of range!\n");
> -			return -EINVAL;
> -		}
> -
> -		return 0;
> -	}
> -
> -	if (rec->flags & FTRACE_FL_REGS)
> -		tramp = mod->arch.tramp_regs;
> -	else
> -		tramp = mod->arch.tramp;
> -
> -	if (module_trampoline_target(mod, tramp, &ptr)) {
> -		pr_err("Failed to get trampoline target\n");
> -		return -EFAULT;
> -	}
> -
> -	pr_devel("trampoline target %lx", ptr);
> -
> -	entry = ppc_global_function_entry((void *)addr);
> -	/* This should match what was called */
> -	if (ptr != entry) {
> -		pr_err("addr %lx does not match expected %lx\n", ptr, entry);
> -		return -EINVAL;
> -	}
> -
> -	if (patch_branch((u32 *)ip, tramp, BRANCH_SET_LINK)) {
> -		pr_err("REL24 out of range!\n");
> -		return -EINVAL;
> -	}
> -
> -	return 0;
> -}
> -#else
> -static int __ftrace_modify_call(struct dyn_ftrace *rec, unsigned long old_addr, unsigned long addr)
> -{
> -	return 0;
> -}
> -#endif
> -
> -int ftrace_modify_call(struct dyn_ftrace *rec, unsigned long old_addr,
> -			unsigned long addr)
> -{
> -	unsigned long ip = rec->ip;
> +	unsigned long tramp, tramp_old, ip = rec->ip;
>   	ppc_inst_t old, new;
> +	struct module *mod;
>   
> -	/*
> -	 * If the calling address is more that 24 bits away,
> -	 * then we had to use a trampoline to make the call.
> -	 * Otherwise just update the call site.
> -	 */
> -	if (test_24bit_addr(ip, addr) && test_24bit_addr(ip, old_addr)) {
> -		/* within range */
> -		old = ftrace_call_replace(ip, old_addr, 1);
> -		new = ftrace_call_replace(ip, addr, 1);
> +	if (is_offset_in_branch_range(old_addr - ip) && is_offset_in_branch_range(addr - ip)) {
> +		/* Within range */
> +		old = ftrace_create_branch_inst(ip, old_addr, 1);
> +		new = ftrace_create_branch_inst(ip, addr, 1);
>   		return ftrace_modify_code(ip, old, new);
>   	} else if (core_kernel_text(ip)) {
>   		/*
> @@ -246,20 +125,22 @@ int ftrace_modify_call(struct dyn_ftrace *rec, unsigned long old_addr,
>   		 * variant, so there is nothing to do here
>   		 */
>   		return 0;
> -	} else if (!IS_ENABLED(CONFIG_MODULES)) {
> -		/* We should not get here without modules */
> -		return -EINVAL;
> +	} else if (IS_ENABLED(CONFIG_MODULES)) {
> +		/* Module code would be going to one of the module stubs */
> +		mod = rec->arch.mod;
> +		if (addr == (unsigned long)ftrace_caller) {
> +			tramp_old = mod->arch.tramp_regs;
> +			tramp = mod->arch.tramp;
> +		} else {
> +			tramp_old = mod->arch.tramp;
> +			tramp = mod->arch.tramp_regs;
> +		}
> +		old = ftrace_create_branch_inst(ip, tramp_old, 1);
> +		new = ftrace_create_branch_inst(ip, tramp, 1);
> +		return ftrace_modify_code(ip, old, new);
>   	}
>   
> -	/*
> -	 * Out of range jumps are called from modules.
> -	 */
> -	if (!rec->arch.mod) {
> -		pr_err("No module loaded\n");
> -		return -EINVAL;
> -	}
> -
> -	return __ftrace_modify_call(rec, old_addr, addr);
> +	return -EINVAL;
>   }
>   #endif
>   

  reply	other threads:[~2023-06-23  5:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19  9:47 [PATCH 00/17] powerpc/ftrace: refactor and add support for -fpatchable-function-entry Naveen N Rao
2023-06-19  9:47 ` [PATCH 01/17] powerpc/ftrace: Fix dropping weak symbols with older toolchains Naveen N Rao
2023-06-23  5:10   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 02/17] powerpc/module: Remove unused .ftrace.tramp section Naveen N Rao
2023-06-23  5:12   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 03/17] powerpc64/ftrace: Move ELFv1 and -pg support code into a separate file Naveen N Rao
2023-06-23  5:13   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 04/17] powerpc/ftrace: Simplify function_graph support in ftrace.c Naveen N Rao
2023-06-23  5:14   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 05/17] powerpc/ftrace: Use FTRACE_REGS_ADDR to identify the correct ftrace trampoline Naveen N Rao
2023-06-23  5:15   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 06/17] powerpc/ftrace: Extend ftrace support for large kernels to ppc32 Naveen N Rao
2023-06-23  5:21   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 07/17] powerpc/ftrace: Consolidate ftrace support into fewer files Naveen N Rao
2023-06-23  5:25   ` Christophe Leroy
2023-06-28  7:32     ` Naveen N Rao
2023-06-19  9:47 ` [PATCH 08/17] powerpc/ftrace: Refactor ftrace_modify_code() Naveen N Rao
2023-06-23  5:27   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 09/17] powerpc/ftrace: Stop re-purposing linker generated long branches for ftrace Naveen N Rao
2023-06-23  5:28   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 10/17] powerpc/ftrace: Add separate ftrace_init_nop() with additional validation Naveen N Rao
2023-06-23  5:29   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 11/17] powerpc/ftrace: Simplify ftrace_make_nop() Naveen N Rao
2023-06-23  5:30   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 12/17] powerpc/ftrace: Simplify ftrace_make_call() Naveen N Rao
2023-06-23  5:30   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 13/17] powerpc/ftrace: Simplify ftrace_modify_call() Naveen N Rao
2023-06-23  5:31   ` Christophe Leroy [this message]
2023-06-19  9:47 ` [PATCH 14/17] powerpc/ftrace: Replace use of ftrace_call_replace() with ftrace_create_branch_inst() Naveen N Rao
2023-06-23  5:32   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 15/17] powerpc/ftrace: Implement ftrace_replace_code() Naveen N Rao
2023-06-23  5:32   ` Christophe Leroy
2023-06-19  9:47 ` [PATCH 16/17] powerpc/ftrace: Add support for -fpatchable-function-entry Naveen N Rao
2023-06-23  5:37   ` Christophe Leroy
2023-06-28  7:40     ` Naveen N Rao
2023-06-19  9:47 ` [PATCH 17/17] powerpc/ftrace: Create a dummy stackframe to fix stack unwind Naveen N Rao
2023-06-23  5:40   ` Christophe Leroy
2023-06-28  7:43     ` Naveen N Rao
2023-08-23 11:55 ` [PATCH 00/17] powerpc/ftrace: refactor and add support for -fpatchable-function-entry Michael Ellerman

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=5011fa7e-a228-9ef2-2dff-9ca1931df26f@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=naveen@kernel.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;
as well as URLs for NNTP newsgroup(s).