linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Naveen N Rao <naveen@kernel.org>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: [RFC PATCH 13/15] powerpc/ftrace: Replace use of ftrace_call_replace() with ftrace_create_branch_inst()
Date: Wed,  7 Jun 2023 22:25:28 +0530	[thread overview]
Message-ID: <8ac06ab617ef7ddfff0b2425e8c670a73b6cb49e.1686151854.git.naveen@kernel.org> (raw)
In-Reply-To: <cover.1686151854.git.naveen@kernel.org>

ftrace_create_branch_inst() is clearer about its intent than
ftrace_call_replace().

Signed-off-by: Naveen N Rao <naveen@kernel.org>
---
 arch/powerpc/kernel/trace/ftrace.c | 17 ++---------------
 1 file changed, 2 insertions(+), 15 deletions(-)

diff --git a/arch/powerpc/kernel/trace/ftrace.c b/arch/powerpc/kernel/trace/ftrace.c
index c810343d1a6cd6..4375ef71609c0a 100644
--- a/arch/powerpc/kernel/trace/ftrace.c
+++ b/arch/powerpc/kernel/trace/ftrace.c
@@ -41,19 +41,6 @@ static ppc_inst_t ftrace_create_branch_inst(unsigned long ip, unsigned long addr
 	return op;
 }
 
-static ppc_inst_t
-ftrace_call_replace(unsigned long ip, unsigned long addr, int link)
-{
-	ppc_inst_t op;
-
-	addr = ppc_function_entry((void *)addr);
-
-	/* if (link) set op to 'bl' else 'b' */
-	create_branch(&op, (u32 *)ip, addr, link ? BRANCH_SET_LINK : 0);
-
-	return op;
-}
-
 static inline int ftrace_read_inst(unsigned long ip, ppc_inst_t *op)
 {
 	if (copy_inst_from_kernel_nofault(op, (void *)ip)) {
@@ -275,14 +262,14 @@ int ftrace_update_ftrace_func(ftrace_func_t func)
 	int ret;
 
 	old = ppc_inst_read((u32 *)&ftrace_call);
-	new = ftrace_call_replace(ip, (unsigned long)func, 1);
+	new = ftrace_create_branch_inst(ip, ppc_function_entry(func), 1);
 	ret = ftrace_modify_code(ip, old, new);
 
 	/* Also update the regs callback function */
 	if (IS_ENABLED(CONFIG_DYNAMIC_FTRACE_WITH_REGS) && !ret) {
 		ip = (unsigned long)(&ftrace_regs_call);
 		old = ppc_inst_read((u32 *)&ftrace_regs_call);
-		new = ftrace_call_replace(ip, (unsigned long)func, 1);
+		new = ftrace_create_branch_inst(ip, ppc_function_entry(func), 1);
 		ret = ftrace_modify_code(ip, old, new);
 	}
 
-- 
2.40.1


  parent reply	other threads:[~2023-06-07 17:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 16:55 [RFC PATCH 00/15] powerpc/ftrace: refactoring and support for -fpatchable-function-entry Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 01/15] powerpc/module: Remove unused .ftrace.tramp section Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 02/15] powerpc64/ftrace: Move ELFv1 and -pg support code into a separate file Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 03/15] powerpc/ftrace: Simplify function_graph support in ftrace.c Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 04/15] powerpc/ftrace: Use FTRACE_REGS_ADDR to identify the correct ftrace trampoline Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 05/15] powerpc/ftrace: Extend ftrace support for large kernels to ppc32 Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 06/15] powerpc/ftrace: Consolidate ftrace support into fewer files Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 07/15] powerpc/ftrace: Refactor ftrace_modify_code() Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 08/15] powerpc/ftrace: Stop re-purposing linker generated long branches for ftrace Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 09/15] powerpc/ftrace: Add separate ftrace_init_nop() with additional validation Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 10/15] powerpc/ftrace: Simplify ftrace_make_nop() Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 11/15] powerpc/ftrace: Simplify ftrace_make_call() Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 12/15] powerpc/ftrace: Simplify ftrace_modify_call() Naveen N Rao
2023-06-07 16:55 ` Naveen N Rao [this message]
2023-06-07 16:55 ` [RFC PATCH 14/15] powerpc/ftrace: Implement ftrace_replace_code() Naveen N Rao
2023-06-07 16:55 ` [RFC PATCH 15/15] powerpc/ftrace: Add support for -fpatchable-function-entry 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=8ac06ab617ef7ddfff0b2425e8c670a73b6cb49e.1686151854.git.naveen@kernel.org \
    --to=naveen@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --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).