linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question about config UPROBES and UPROBE_EVENTS
Date: Tue, 1 Oct 2024 08:32:44 -0400	[thread overview]
Message-ID: <20241001083244.486589b9@gandalf.local.home> (raw)
In-Reply-To: <20240930113231.6c87108d@gandalf.local.home>

On Mon, 30 Sep 2024 11:32:31 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> > uprobe_register/unregister APIs are exposed to the kernel modules,
> > since systemtap had been introduced this feature.
> >  
> 
> OK, but since they have always been visible, I would just make
> CONFIG_UPROBES a normal option and CONFIG_UPROBE_EVENTS select it if it
> gets selected, and not depend on it.

Thinking about this more, since systemtap is out of tree, and if that's the
only user of uprobes, I don't think it should be exposed as a prompt.

If you want uprobes for systemtap, you must also have uprobe events.

-- Steve

      parent reply	other threads:[~2024-10-01 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  6:40 Question about config UPROBES and UPROBE_EVENTS Tiezhu Yang
2024-09-11 13:43 ` Steven Rostedt
2024-09-29 23:15 ` Masami Hiramatsu
2024-09-30  1:33   ` Tiezhu Yang
2024-09-30 14:06     ` Steven Rostedt
2024-09-30 15:28       ` Masami Hiramatsu
2024-09-30 15:32         ` Steven Rostedt
2024-09-30 15:43           ` Masami Hiramatsu
2024-10-01  6:30             ` Tiezhu Yang
2024-10-01 12:30               ` Steven Rostedt
2024-10-01 12:33                 ` Steven Rostedt
2024-10-01 12:32           ` Steven Rostedt [this message]

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=20241001083244.486589b9@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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).