From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Michael Ellerman <patch-notifications@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
Abhishek Dubey <adubey@linux.ibm.com>,
naveen@kernel.org, hbathini@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, mhiramat@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v4 RESEND] powerpc: Replace kretprobe code with rethook on powerpc
Date: Sun, 8 Sep 2024 22:10:53 +0900 [thread overview]
Message-ID: <20240908221053.ad2ed73bf42db9273aac419c@kernel.org> (raw)
In-Reply-To: <172562357215.467568.2172858907419105155.b4-ty@ellerman.id.au>
On Fri, 06 Sep 2024 21:52:52 +1000
Michael Ellerman <patch-notifications@ellerman.id.au> wrote:
> On Fri, 30 Aug 2024 07:31:31 -0400, Abhishek Dubey wrote:
> > This is an adaptation of commit f3a112c0c40d ("x86,rethook,kprobes:
> > Replace kretprobe with rethook on x86") to powerpc.
> >
> > Rethook follows the existing kretprobe implementation, but separates
> > it from kprobes so that it can be used by fprobe (ftrace-based
> > function entry/exit probes). As such, this patch also enables fprobe
> > to work on powerpc. The only other change compared to the existing
> > kretprobe implementation is doing the return address fixup in
> > arch_rethook_fixup_return().
> >
> > [...]
>
> Applied to powerpc/next.
>
> [1/1] powerpc: Replace kretprobe code with rethook on powerpc
> https://git.kernel.org/powerpc/c/19f1bc3fb55452739dd3d56cfd06c29ecdbe3e9f
Thanks, and sorry for late reply, but I don't have any objection.
>
> cheers
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-09-08 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 11:31 [PATCH v4 RESEND] powerpc: Replace kretprobe code with rethook on powerpc Abhishek Dubey
2024-09-03 6:48 ` Michael Ellerman
2024-09-06 11:52 ` Michael Ellerman
2024-09-08 13:10 ` Masami Hiramatsu [this message]
2024-09-09 1:13 ` Andrii Nakryiko
2024-09-09 6:40 ` 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=20240908221053.ad2ed73bf42db9273aac419c@kernel.org \
--to=mhiramat@kernel.org \
--cc=adubey@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=patch-notifications@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.