Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1238372 > unrolled thread

[PATCH] ebpf, events: make it actually more configurable

Back to article view | Back to linux.kernel

Contents

  [PATCH] ebpf, events: make it actually more configurable Daniel Borkmann <daniel@iogearbox.net> - 2015-10-02 17:50 +0200
    Re: [PATCH] ebpf, events: make it actually more configurable Ingo Molnar <mingo@kernel.org> - 2015-10-03 08:40 +0200
      Re: [PATCH] ebpf, events: make it actually more configurable Daniel Borkmann <daniel@iogearbox.net> - 2015-10-03 09:50 +0200
        Re: [PATCH] ebpf, events: make it actually more configurable Ingo Molnar <mingo@kernel.org> - 2015-10-03 10:30 +0200
          Re: [PATCH] ebpf, events: make it actually more configurable Daniel Borkmann <daniel@iogearbox.net> - 2015-10-05 00:20 +0200

#1238372 — [PATCH] ebpf, events: make it actually more configurable

While testing some other BPF issue, I realized that BPF_EVENTS is
actually not accessible through menuconfig because of a missing
description that needs to be attached to the bool. After the patch
the entry shows up in menuconfig and can be enabled/disabled from
there.

Fixes: e1abf2cc8d5d ("bpf: Fix the build on BPF_SYSCALL=y && !CONFIG_TRACING kernels, make it more configurable")
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@plumgrid.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
---
 kernel/trace/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 1153c43..db9a8c4 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -433,9 +433,9 @@ config UPROBE_EVENT
 	  of perf tools on user space applications.
 
 config BPF_EVENTS
+	bool "Enable BPF programs to be attached to events"
 	depends on BPF_SYSCALL
 	depends on KPROBE_EVENT || UPROBE_EVENT
-	bool
 	default y
 	help
 	  This allows the user to attach BPF programs to kprobe events.
-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1238743

* Daniel Borkmann <daniel@iogearbox.net> wrote:

> While testing some other BPF issue, I realized that BPF_EVENTS is
> actually not accessible through menuconfig because of a missing
> description that needs to be attached to the bool. After the patch
> the entry shows up in menuconfig and can be enabled/disabled from
> there.

Yeah, so the principle is the following: the main configuration option for it is 
BPF_SYSCALL. The BPF_EVENTS is an internal detail, always enabled when possible, 
and we make it so that if the BPF syscall is enabled, we'll enable the perf 
integration if all the must-have components are in place:

>  	depends on KPROBE_EVENT || UPROBE_EVENT
>  	default y

So this is intentional.

Unless your suggestion is to also enable it when neither KPROBE_EVENT nor 
UPROBE_EVENT are defined. Does that make sense?

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1238753

On 10/03/2015 08:37 AM, Ingo Molnar wrote:
>
> * Daniel Borkmann <daniel@iogearbox.net> wrote:
>
>> While testing some other BPF issue, I realized that BPF_EVENTS is
>> actually not accessible through menuconfig because of a missing
>> description that needs to be attached to the bool. After the patch
>> the entry shows up in menuconfig and can be enabled/disabled from
>> there.
>
> Yeah, so the principle is the following: the main configuration option for it is
> BPF_SYSCALL. The BPF_EVENTS is an internal detail, always enabled when possible,
> and we make it so that if the BPF syscall is enabled, we'll enable the perf
> integration if all the must-have components are in place:

Makes sense, yes. I probably got confused due to the help text on the
hidden Kconfig entry, but that can nevertheless serve as documentation
purpose.

Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1238774

* Daniel Borkmann <daniel@iogearbox.net> wrote:

> On 10/03/2015 08:37 AM, Ingo Molnar wrote:
> >
> >* Daniel Borkmann <daniel@iogearbox.net> wrote:
> >
> >>While testing some other BPF issue, I realized that BPF_EVENTS is
> >>actually not accessible through menuconfig because of a missing
> >>description that needs to be attached to the bool. After the patch
> >>the entry shows up in menuconfig and can be enabled/disabled from
> >>there.
> >
> > Yeah, so the principle is the following: the main configuration option for it 
> > is BPF_SYSCALL. The BPF_EVENTS is an internal detail, always enabled when 
> > possible, and we make it so that if the BPF syscall is enabled, we'll enable 
> > the perf integration if all the must-have components are in place:
> 
> Makes sense, yes. I probably got confused due to the help text on the hidden 
> Kconfig entry, but that can nevertheless serve as documentation purpose.

Feel free to send a patch that adds a sentence to that help text that explains 
that this is an internal helper Kconfig entry that does not need to be 
interactively configurable.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1239231

On 10/03/2015 10:24 AM, Ingo Molnar wrote:
...
> Feel free to send a patch that adds a sentence to that help text that explains
> that this is an internal helper Kconfig entry that does not need to be
> interactively configurable.

Sorry for the late reply. I think it's actually fine as-is, noticed that the
same is being done various times in this Kconfig.

Thanks again,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web