From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, bpf <bpf@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
adubey@linux.ibm.com,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
KP Singh <kpsingh@chromium.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Will Deacon <will@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Florent Revest <revest@chromium.org>,
Puranjay Mohan <puranjay@kernel.org>
Subject: Re: Unsupported CONFIG_FPROBE and CONFIG_RETHOOK on ARM64
Date: Thu, 12 Sep 2024 08:53:46 +0900 [thread overview]
Message-ID: <20240912085346.154b18ca686c7c4595e93c9a@kernel.org> (raw)
In-Reply-To: <CAEf4BzaWtsAeXyDWh7kq8Qnyy=9u7iAVonmefNRvXnTfbv03yg@mail.gmail.com>
On Wed, 11 Sep 2024 13:18:12 -0700
Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
> > > So while I get the desire to have a clean and nice
> > > end goal, and that it might take a bit longer to get everything right.
> > > But, maybe, landing a stop-gap solution meanwhile (especially as
> > > isolated and thus easily backportable as the patch [0] you referenced)
> > > is an OK path forward?
> >
> > I had not realized that the PSTATE register was not saved correctly
> > at that point. This is one reason why I decided to move in the
> > current fprobe-on-fgraph direction.
>
> Sure, but you said yourself, the same problem exists with current
> kretprobe implementation, so this won't regress anything. And yes,
> your fprobe-on-fgraph series is supposed to fix this for good, which
> is great, but that's a separate topic.
It does not regress kretprobe, but introduces the same problem to
fprobe. And since fprobe-on-fgraph was boosted by this problem,
I think that is not a separate topic.
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-09-11 23:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 1:02 Unsupported CONFIG_FPROBE and CONFIG_RETHOOK on ARM64 Andrii Nakryiko
2024-09-10 18:23 ` Andrii Nakryiko
2024-09-10 18:40 ` Steven Rostedt
2024-09-10 18:54 ` Steven Rostedt
2024-09-10 20:29 ` Andrii Nakryiko
2024-09-10 22:22 ` Steven Rostedt
2024-09-11 0:27 ` Andrii Nakryiko
2024-09-11 1:27 ` Steven Rostedt
2024-09-11 1:32 ` Steven Rostedt
2024-09-11 0:39 ` Masami Hiramatsu
2024-09-11 0:44 ` Andrii Nakryiko
2024-09-11 15:26 ` Masami Hiramatsu
2024-09-11 20:21 ` Andrii Nakryiko
2024-09-11 0:13 ` Masami Hiramatsu
2024-09-11 0:37 ` Andrii Nakryiko
2024-09-11 15:18 ` Masami Hiramatsu
2024-09-11 20:18 ` Andrii Nakryiko
2024-09-11 23:53 ` Masami Hiramatsu [this message]
2024-09-12 18:38 ` Andrii Nakryiko
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=20240912085346.154b18ca686c7c4595e93c9a@kernel.org \
--to=mhiramat@kernel.org \
--cc=adubey@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=puranjay@kernel.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.org \
--cc=will@kernel.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