[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241001083339.612395ba@gandalf.local.home>
Date: Tue, 1 Oct 2024 08:33:39 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>
Cc: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Question about config UPROBES and UPROBE_EVENTS
On Tue, 1 Oct 2024 08:30:42 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Tue, 1 Oct 2024 14:30:33 +0800
> Tiezhu Yang <yangtiezhu@...ngson.cn> wrote:
>
> > Then, CONFIG_KPROBE_EVENTS should depend on or select CONFIG_KPROBES?
> > In the current code, CONFIG_KPROBE_EVENTS depend on CONFIG_KPROBES,
> > the CONFIG_KPROBE_EVENTS menu is hidden if CONFIG_KPROBES is not set.
>
> We could just for consistency. KPROBE_EVENTS would then need to depend on
> HAVE_KPROBES as well. It does add some duplication.
>
I take this back. I don't think there's any reason to have a UPROBES prompt.
If you want UPROBES, you should have UPROBE_EVENTS. They are completely
different than kprobes.
-- Steve
Powered by blists - more mailing lists