From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751894AbbJCHmy (ORCPT ); Sat, 3 Oct 2015 03:42:54 -0400 Received: from www62.your-server.de ([213.133.104.62]:54294 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751667AbbJCHmx (ORCPT ); Sat, 3 Oct 2015 03:42:53 -0400 Message-ID: <560F86FB.3070200@iogearbox.net> Date: Sat, 03 Oct 2015 09:42:51 +0200 From: Daniel Borkmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Ingo Molnar CC: linux-kernel@vger.kernel.org, Alexei Starovoitov , Steven Rostedt Subject: Re: [PATCH] ebpf, events: make it actually more configurable References: <20151003063715.GA22713@gmail.com> In-Reply-To: <20151003063715.GA22713@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/03/2015 08:37 AM, Ingo Molnar wrote: > > * Daniel Borkmann 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