[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151003082448.GA27061@gmail.com>
Date: Sat, 3 Oct 2015 10:24:48 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: linux-kernel@...r.kernel.org,
Alexei Starovoitov <ast@...mgrid.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] ebpf, events: make it actually more configurable
* Daniel Borkmann <daniel@...earbox.net> wrote:
> On 10/03/2015 08:37 AM, Ingo Molnar wrote:
> >
> >* Daniel Borkmann <daniel@...earbox.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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists