public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: He Kuang <hekuang@huawei•com>
To: Alexei Starovoitov <ast@plumgrid•com>,
	Steven Rostedt <rostedt@goodmis•org>
Cc: Ingo Molnar <mingo@kernel•org>,
	Namhyung Kim <namhyung@kernel•org>,
	Arnaldo Carvalho de Melo <acme@infradead•org>,
	Jiri Olsa <jolsa@redhat•com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi•com>,
	Linux API <linux-api@vger•kernel.org>,
	Network Development <netdev@vger•kernel.org>,
	LKML <linux-kernel@vger•kernel.org>,
	Linus Torvalds <torvalds@linux-foundation•org>,
	Peter Zijlstra <peterz@infradead•org>,
	"Eric W. Biederman" <ebiederm@xmission•com>,
	<wangnan0@huawei•com>
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	[thread overview]
Message-ID: <54E1D3F6.3040500@huawei.com> (raw)
In-Reply-To: <CAMEtUuzY_Po=WtFEFg1aqzJ8dEF4rHGcWDsaS44KYgACMNPPgA@mail.gmail.com>

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?

  parent reply	other threads:[~2015-02-16 11:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  0:22 [PATCH v3 linux-trace 1/8] tracing: attach eBPF programs to tracepoints and syscalls Alexei Starovoitov
2015-02-11  9:33 ` Peter Zijlstra
     [not found] ` <CAMEtUuzY_Po=WtFEFg1aqzJ8dEF4rHGcWDsaS44KYgACMNPPgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-11  0:50   ` Steven Rostedt
2015-02-11  9:45   ` Peter Zijlstra
2015-02-11 10:15   ` Peter Zijlstra
2015-02-12  4:58   ` Hekuang
2015-02-16 11:26 ` He Kuang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-23 18:55 Alexei Starovoitov
2015-02-14 23:02 Alexei Starovoitov
2015-02-14 22:54 Alexei Starovoitov
2015-02-14 22:48 Alexei Starovoitov
2015-02-11  6:33 Alexei Starovoitov
     [not found] ` <CAMEtUuxizvHF09y_vU-c+L=n16tqWDqJPTybGB1a_OqN7p+jsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-11 12:51   ` Steven Rostedt
2015-02-11  3:04 Alexei Starovoitov
     [not found] ` <CAMEtUuy+B9aXP-8m7tA6aNxnS4SKRhMpfGEdWMcbxbj7ggOATw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-11  4:31   ` Steven Rostedt
2015-02-10 19:53 Alexei Starovoitov
     [not found] ` <CAMEtUuwAf4AFeWVEdJB4VQz_=2fWY=q8=rbkFg38rtVtNVCHxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-10 21:53   ` Steven Rostedt
     [not found]     ` <20150210165359.34cc53d9-f9ZlEuEWxVcJvu8Pb33WZ0EMvNT87kid@public.gmane.org>
2015-02-11 10:28       ` Peter Zijlstra
2015-02-10  6:10 Alexei Starovoitov
     [not found] ` <CAMEtUuztTca2jC9Su0YkTHEUHsD4p2PBRyukabrjGO0WfFzdfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-10 13:05   ` Steven Rostedt
2015-02-10  5:51 Alexei Starovoitov
2015-02-10 12:27 ` Steven Rostedt
2015-02-10  3:45 [PATCH v3 linux-trace 0/8] tracing: attach eBPF programs to tracepoints/syscalls/kprobe Alexei Starovoitov
     [not found] ` <1423539961-21792-1-git-send-email-ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org>
2015-02-10  3:45   ` [PATCH v3 linux-trace 1/8] tracing: attach eBPF programs to tracepoints and syscalls Alexei Starovoitov
     [not found]     ` <1423539961-21792-2-git-send-email-ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org>
2015-02-10  4:46       ` Steven Rostedt
2015-02-10  5:13       ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E1D3F6.3040500@huawei.com \
    --to=hekuang@huawei$(echo .)com \
    --cc=acme@infradead$(echo .)org \
    --cc=ast@plumgrid$(echo .)com \
    --cc=ebiederm@xmission$(echo .)com \
    --cc=jolsa@redhat$(echo .)com \
    --cc=linux-api@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=masami.hiramatsu.pt@hitachi$(echo .)com \
    --cc=mingo@kernel$(echo .)org \
    --cc=namhyung@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=peterz@infradead$(echo .)org \
    --cc=rostedt@goodmis$(echo .)org \
    --cc=torvalds@linux-foundation$(echo .)org \
    --cc=wangnan0@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox