Re: [RFC PATCH 00/22] perf tools: introduce 'perf bpf' command to load eBPF programs.

[Ingo Molnar <mingo@kernel.org>]

* Alexei Starovoitov <ast@plumgrid.com> wrote:

> On 5/1/15 4:49 AM, Ingo Molnar wrote:
> >
> >* Peter Zijlstra <peterz@infradead.org> wrote:
> >
> >>On Thu, Apr 30, 2015 at 09:37:04PM -0700, Alexei Starovoitov wrote:
> >>>We're also working in parallel on creating a new tracing language
> >>>that together with llvm backend can be used as a single shared library
> >>>that can be called from perf or anything else.
> >>
> >>Gurgh, please also keep normal C an option. [...]
> >
> >Absolutely, I thought there was agreement on that when we started
> >merging all these eBPF patches ...
> >
> >It might be 'simplified C', in that it's just a subset of C, but
> >please don't re-do something that works, especially if it's used to
> >instrument a kernel that is written in C ...
> 
> of course. When did I say that I like 'bird' languages? :)
> By 'new' I mean that we're not trying to port existing tracing
> language like dtrace, systemtap, ktap to bpf.
> I believe dtrace would have been more widely adopted if it didn't
> invent new syntax. We're trying to do a C -- with ++.
> It's C where non-supported things like 'for', 'while', 'asm' are
> actively error-ed by front-end and additional syntactic
> sugar for things that too ugly/verbose in vanilla C are added.

Ok, sounds very good to me!

Thanks,

	Ingo