Userspace eBPF VM
This project aims to create an Apache-licensed library for executing eBPF programs. The primary implementation of eBPF lives in the Linux kernel, but due to its GPL license it can't be used in many projects.
Linux documentation for the eBPF instruction set
This project includes an eBPF assembler, disassembler, interpreter (for all platforms), and JIT compiler (for x86-64 and Arm64 targets).
Before following any of the instructions below for building, testing, contributing, etc, please be sure to properly check out the source code which requires properly initializing submodules:
git submodule update --init --recursive
In order to prepare your system to successfully generate the build system using CMake, follow the platform-specific instructions below.
Building, compiling and testing on Windows requires an installation of Visual Studio (not VS Code -- the MSVC compiler is necessary!).
Note: There are free-to-use versions of Visual Studio for individual developers. These versions are known as the community version.
You can build, compile and test uBPF using VS Code but Visual Studio is still required.
The other requirement is that you have nuget.exe
in your PATH
. You can determine if your host meets this criteria by testing whether
> nuget.exe
produces output about how to execute the program. With nuget.exe
installed, the cmake
configuration system will download all the required developer libraries as it configures the build system.
First, make sure that you have the XCode Command Line Tools installed:
$ xcode-select --install
Installing the XCode Command Linux Tools will install Apple's version of the Clang compiler and other developer-support tools.
uBpf requires that your host have several support libraries installed. The easiest way to configure your host to meet these requirements,
$ brew install boost
$ brew install llvm cmake $ brew install clang-format
Installing LLVM from Homebrew is optional for developing and using uBPF on macOS. It is required if you plan on compiling/creating eBPF programs by compiling LLVM and storing them in ELF files. If you do install LLVM from Homebrew, add -DUBPF_ALTERNATE_LLVM_PATH=/opt/homebrew/opt/llvm/bin
to the cmake
configuration command:
cmake -S . -B build -DUBPF_ENABLE_TESTS=true -DUBPF_ALTERNATE_LLVM_PATH=/opt/homebrew/opt/llvm/bin
./scripts/build-libbpf.sh
A build system for compiling and testing ubpf is generated for Windows, Linux and macOS platforms using cmake
:
cmake -S . -B build -DUBPF_ENABLE_TESTS=true cmake --build build --config Debug
cmake --build build --target test --
ctest --test-dir build
We love contributions!
We aim to maintain code coverage with every code change. The CI/CD pipeline will verify this invariant as part of the contribution process. However, you can calculate code coverage locally by
coveralls --gcov-options '\-lp' -i $PWD/vm/ubpf_vm.c -i $PWD/vm/ubpf_jit_x86_64.c -i $PWD/vm/ubpf_loader.c
We also aim to maintain a consistent code format. The pre-commit git hooks configured for the uBPF repository will guarantee that code changes match the format we expect. In order for those hooks to work effectively, you must have clang-format
installed and available on your system.
You'll need Clang 3.7.
clang-3.7 -O2 -target bpf -c prog.c -o prog.o
You can then pass the contents of prog.o
to ubpf_load_elf
, or to the stdin of the vm/test
binary.
Copyright 2015, Big Switch Networks, Inc. Licensed under the Apache License, Version 2.0 <LICENSE.txt or http://www.apache.org/licenses/LICENSE-2.0>.