From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question about config UPROBES and UPROBE_EVENTS
Date: Mon, 30 Sep 2024 09:33:42 +0800 [thread overview]
Message-ID: <f639079e-bc1c-7f2a-4c3f-de1a6780da84@loongson.cn> (raw)
In-Reply-To: <20240930081529.f6f9161c20db9b95c9b46252@kernel.org>
On 09/30/2024 07:15 AM, Masami Hiramatsu (Google) wrote:
> On Wed, 11 Sep 2024 14:40:56 +0800
> Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>
>> Hi Masami,
>>
>> I am a little confused about config UPROBES and UPROBE_EVENTS.
>> Uprobes is the user-space counterpart to kprobes, I want to do
>> some small changes:
>>
>> (1) since config KPROBES can be selectable, just make config UPROBES
>> selectable too.
>>
>> (2) since config KPROBE_EVENTS depends on KPROBES rather than select
>> KPROBES, just make config UPROBE_EVENTS depends on UPROBES rather
>> than select UPROBES.
>>
>> Could you please let me know are you OK with the following changes?
>> If yes, I will send formal patches later.
>
> Hm, I don't completely reject this idea,
Thanks for your reply. I have almost dropped this idea due to my
thoughtless after receiving the reply of Steven Rostedt [1].
> but I'm not sure about the benefits
> to users and keeping backward compatibility.
Yes, I think so too.
> Especially, the latter one
> may hide uprobe_events by default.
Yes.
> As you can see, the CONFIG_KPROBES is
> enabled by default, thus it does not hide the CONFIG_KPROBE_EVENTS.But
Maybe I missed something, AFAICT, the CONFIG_KPROBES is disabled by
default, it needs to enable manually by the users, and also we can
not see the CONFIG_KPROBE_EVENTS menu if CONFIG_KPROBES is not set
because CONFIG_KPROBE_EVENTS depends on CONFIG_KPROBES.
> the CONFIG_UPROBES is disabled by default and make CONFIG_UPROBE_EVENTS
> depending on it, the uprobe_events menu is hidden. I don't like this.
This is somehow like the current status of CONFIG_KPROBES and
CONFIG_KPROBE_EVENTS.
[1] https://lore.kernel.org/all/20240911094317.4a28fc3b@gandalf.local.home/
Thanks,
Tiezhu
next prev parent reply other threads:[~2024-09-30 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 6:40 Tiezhu Yang
2024-09-11 13:43 ` Steven Rostedt
2024-09-29 23:15 ` Masami Hiramatsu
2024-09-30 1:33 ` Tiezhu Yang [this message]
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
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=f639079e-bc1c-7f2a-4c3f-de1a6780da84@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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
all inboxes | Powered by JetHome®