From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755753AbbBPL3Y (ORCPT ); Mon, 16 Feb 2015 06:29:24 -0500 Received: from szxga01-in.huawei.com ([119.145.14.64]:5796 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755347AbbBPL3W (ORCPT ); Mon, 16 Feb 2015 06:29:22 -0500 Message-ID: <54E1D3F6.3040500@huawei.com> Date: Mon, 16 Feb 2015 19:26:46 +0800 From: He Kuang User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Alexei Starovoitov , Steven Rostedt CC: Ingo Molnar , Namhyung Kim , Arnaldo Carvalho de Melo , Jiri Olsa , Masami Hiramatsu , Linux API , Network Development , LKML , Linus Torvalds , Peter Zijlstra , "Eric W. Biederman" , Subject: Re: [PATCH v3 linux-trace 1/8] tracing: attach eBPF programs to tracepoints and syscalls References: In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.110.54.65] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Alexei Another suggestion on bpf syscall interface. Currently, BPF + syscalls/kprobes depends on CONFIG_BPF_SYSCALL. In kernel used on commercial products, CONFIG_BPF_SYSCALL is probably disabled, in this case, bpf bytecode cannot be loaded to the kernel. If we turn the functionality of BPF_SYSCALL into a loadable module, then we can use it without any dependencies on the kernel. What about change bpf syscall to a /dev node or /sys file which can be exported by a kernel module? From mboxrd@z Thu Jan 1 00:00:00 1970 From: He Kuang Subject: Re: [PATCH v3 linux-trace 1/8] tracing: attach eBPF programs to tracepoints and syscalls Date: Mon, 16 Feb 2015 19:26:46 +0800 Message-ID: <54E1D3F6.3040500@huawei.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Alexei Starovoitov , Steven Rostedt Cc: Ingo Molnar , Namhyung Kim , Arnaldo Carvalho de Melo , Jiri Olsa , Masami Hiramatsu , Linux API , Network Development , LKML , Linus Torvalds , Peter Zijlstra , "Eric W. Biederman" , wangnan0@huawei.com List-Id: linux-api@vger.kernel.org Hi, Alexei Another suggestion on bpf syscall interface. Currently, BPF + syscalls/kprobes depends on CONFIG_BPF_SYSCALL. In kernel used on commercial products, CONFIG_BPF_SYSCALL is probably disabled, in this case, bpf bytecode cannot be loaded to the kernel. If we turn the functionality of BPF_SYSCALL into a loadable module, then we can use it without any dependencies on the kernel. What about change bpf syscall to a /dev node or /sys file which can be exported by a kernel module?