From: Li Huafei <lihuafei1@huawei.com>
To: <guoren@kernel.org>, <mhiramat@kernel.org>, <palmer@dabbelt.com>
Cc: <rostedt@goodmis.org>, <mingo@redhat.com>,
<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
<naveen.n.rao@linux.ibm.com>, <anil.s.keshavamurthy@intel.com>,
<davem@davemloft.net>, <jszhang@kernel.org>,
<peterz@infradead.org>, <liaochang1@huawei.com>, <me@packi.ch>,
<penberg@kernel.org>, <lihuafei1@huawei.com>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] riscv: ftrace: Fix the comments about the number of ftrace instruction
Date: Tue, 26 Apr 2022 09:57:50 +0800 [thread overview]
Message-ID: <20220426015751.88582-1-lihuafei1@huawei.com> (raw)
When DYNAMIC_FTRACE is enabled, we put four instructions in front of the
function for ftrace use, not five.
Signed-off-by: Li Huafei <lihuafei1@huawei.com>
---
arch/riscv/kernel/ftrace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/kernel/ftrace.c b/arch/riscv/kernel/ftrace.c
index 4716f4cdc038..63f457650fa4 100644
--- a/arch/riscv/kernel/ftrace.c
+++ b/arch/riscv/kernel/ftrace.c
@@ -73,7 +73,7 @@ static int __ftrace_modify_call(unsigned long hook_pos, unsigned long target,
}
/*
- * Put 5 instructions with 16 bytes at the front of function within
+ * Put 4 instructions with 16 bytes at the front of function within
* patchable function entry nops' area.
*
* 0: REG_S ra, -SZREG(sp)
--
2.17.1
next reply other threads:[~2022-04-26 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 1:57 Li Huafei [this message]
2022-04-26 1:57 ` [PATCH 2/2] riscv: kprobe: Allow coexistence of ftrace and kprobe Li Huafei
2022-04-26 8:01 ` Guo Ren
2022-04-26 8:16 ` Guo Ren
2022-04-29 9:15 ` Li Huafei
2022-04-30 7:08 ` Guo Ren
2022-05-09 6:51 ` Li Huafei
2022-04-26 6:22 ` [PATCH 1/2] riscv: ftrace: Fix the comments about the number of ftrace instruction Guo Ren
2022-04-26 8:52 ` Li Huafei
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=20220426015751.88582-1-lihuafei1@huawei.com \
--to=lihuafei1@huawei.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@packi.ch \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.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).