From: Charlie Jenkins <charlie@rivosinc.com>
To: cp0613@linux.alibaba.com
Cc: corbet@lwn.net, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] Documentation: riscv: Remove KPROBES_ON_FTRACE
Date: Thu, 9 Jan 2025 18:39:33 -0800 [thread overview]
Message-ID: <Z4CIZSpbbUATs8TN@ghost> (raw)
In-Reply-To: <20250108020342.4172-1-cp0613@linux.alibaba.com>
On Wed, Jan 08, 2025 at 10:03:42AM +0800, cp0613@linux.alibaba.com wrote:
> From: Chen Pei <cp0613@linux.alibaba.com>
>
> Since commit 7caa9765465f60 ("ftrace: riscv: move from REGS to ARGS"),
> kprobe on ftrace is not supported by riscv.
>
> And commit 3308172276db5d ("trace: riscv: Remove deprecated kprobe on
> ftrace support") removed the relevant code, but left out the
> documentation, so fix that.
>
> Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
Perhaps this should have a fixes tag for the commit that removed the
support?
Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>
Fixes: 3308172276db5d ("trace: riscv: Remove deprecated kprobe on ftrace support")
> ---
> Documentation/features/debug/kprobes-on-ftrace/arch-support.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/features/debug/kprobes-on-ftrace/arch-support.txt b/Documentation/features/debug/kprobes-on-ftrace/arch-support.txt
> index 02febc883..d937b7a03 100644
> --- a/Documentation/features/debug/kprobes-on-ftrace/arch-support.txt
> +++ b/Documentation/features/debug/kprobes-on-ftrace/arch-support.txt
> @@ -20,7 +20,7 @@
> | openrisc: | TODO |
> | parisc: | ok |
> | powerpc: | ok |
> - | riscv: | ok |
> + | riscv: | TODO |
> | s390: | ok |
> | sh: | TODO |
> | sparc: | TODO |
> --
> 2.43.0
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-01-10 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 2:03 [PATCH] Documentation: riscv: Remove KPROBES_ON_FTRACE cp0613
2025-01-10 2:39 ` Charlie Jenkins [this message]
2025-02-04 17:07 ` Jonathan Corbet
2025-02-13 18:30 ` patchwork-bot+linux-riscv
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=Z4CIZSpbbUATs8TN@ghost \
--to=charlie@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=cp0613@linux.alibaba.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).