BPF List
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.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>,
	Mark Rutland <mark.rutland@arm.com>,
	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: Wed, 11 Sep 2024 09:39:49 +0900	[thread overview]
Message-ID: <20240911093949.40e65804d0e517a1fa1cba11@kernel.org> (raw)
In-Reply-To: <CAEf4BzZRV6h5nitTyQ_zah6wWMBZD6QQBbTCWyPVzkPpS42sgg@mail.gmail.com>

On Tue, 10 Sep 2024 13:29:57 -0700
Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:

> You are probably talking about [0]. But I was asking about [1], i.e.,
> adding HAVE_RETHOOK support to ARM64. Despite all your emotions above,
> can I still get a meaningful answer as for why that wasn't landed and
> what prevents it from landing right now before Masami's 20-patch
> series lands?

As I replied to your last email, Mark discovered that [1] is incorrect.
 From the bpf perspective, it may be fine that struct pt_regs is missing
 some architecture-specific registers, but from an API perspective,
 it is a problem.

Actually kretprobes on arm64 still does not do it correctly, but I also
know most of users does not care. So currently I keep it as it is. But
after fixing this issue on fprobe. I would like to update kretprobe so
that it will use sw-breakpoint to handle it. It will increase the overhead
of kretprobe, but it should be replaced by fprobe at that moment.

Thank you,

> 
>   [0] https://lore.kernel.org/linux-trace-kernel/172398527264.293426.2050093948411376857.stgit@devnote2/
>   [1] https://lore.kernel.org/bpf/164338038439.2429999.17564843625400931820.stgit@devnote2/
> 
> >
> > Again, just letting you know.
> >
> > -- Steve


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  parent reply	other threads:[~2024-09-11  0:39 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 [this message]
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
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=20240911093949.40e65804d0e517a1fa1cba11@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=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