* 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