[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAMEtUuyfQF2eh+YszkmQa9g8kkZ0QZOTHbowa-npRyrV_mnJQQ@mail.gmail.com>
Date: Mon, 26 Jan 2015 21:56:40 -0800
From: Alexei Starovoitov <ast@...mgrid.com>
To: Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Cc: Brendan Gregg <brendan.d.gregg@...il.com>,
Daniel Borkmann <dborkman@...hat.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jovi Zhangwei <jovi.zhangwei@...il.com>,
Jesse Gross <jesse@...ira.com>, Thomas Graf <tgraf@...g.ch>
Subject: BPF backend has landed in LLVM
llvm trunk now has BPF backend:
https://twitter.com/llvmweekly/status/559076464973594625
It's the one used to build samples/bpf/*_kern.c examples.
Compiler just emits extended BPF instructions. It's not
aware whether they are used for tracing or networking,
or how they're loaded into the kernel.
the backend has 'experimental' status,
meaning that it doesn't get configured by default and
one needs to use --enable-experimental-targets=bpf
to build it.
todo list:
- promote it from 'experimental' status by
the time llvm 3.7 is released :)
- write front-end for tracing via mcjit api
llvm will be used as a library: parsing of some
tracing language, codegen, loading of bpf via
syscall will be done from one process
- tighten accepted IR and improve error reporting
(currently it can compile too much of C that
kernel will later reject, so need to make strict)
- test/fix what it emits on arm and other archs
(all little endian should work as-is, big-endian
might need some fixes)
- support 32-bit subregisters
If anyone has spare cycles to help out, it
would be great.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists