Skip to content
  1. Dec 19, 2015
  2. Dec 03, 2015
  3. Oct 28, 2015
  4. Oct 27, 2015
  5. Sep 07, 2015
  6. Aug 13, 2015
  7. Jun 30, 2015
  8. May 05, 2015
  9. Apr 21, 2015
  10. Mar 16, 2015
  11. Mar 05, 2015
  12. Jan 28, 2015
  13. Jan 24, 2015
    • Alexei Starovoitov's avatar
      BPF backend · e4c8c807
      Alexei Starovoitov authored
      Summary:
      V8->V9:
      - cleanup tests
      
      V7->V8:
      - addressed feedback from David:
      - switched to range-based 'for' loops
      - fixed formatting of tests
      
      V6->V7:
      - rebased and adjusted AsmPrinter args
      - CamelCased .td, fixed formatting, cleaned up names, removed unused patterns
      - diffstat: 3 files changed, 203 insertions(+), 227 deletions(-)
      
      V5->V6:
      - addressed feedback from Chandler:
      - reinstated full verbose standard banner in all files
      - fixed variables that were not in CamelCase
      - fixed names of #ifdef in header files
      - removed redundant braces in if/else chains with single statements
      - fixed comments
      - removed trailing empty line
      - dropped debug annotations from tests
      - diffstat of these changes:
        46 files changed, 456 insertions(+), 469 deletions(-)
      
      V4->V5:
      - fix setLoadExtAction() interface
      - clang-formated all where it made sense
      
      V3->V4:
      - added CODE_OWNERS entry for BPF backend
      
      V2->V3:
      - fix metadata in tests
      
      V1->V2:
      - addressed feedback from Tom and Matt
      - removed top level change to configure (now everything via 'experimental-backend')
      - reworked error reporting via DiagnosticInfo (similar to R600)
      - added few more tests
      - added cmake build
      - added Triple::bpf
      - tested on linux and darwin
      
      V1 cover letter:
      ---------------------
      recently linux gained "universal in-kernel virtual machine" which is called
      eBPF or extended BPF. The name comes from "Berkeley Packet Filter", since
      new instruction set is based on it.
      This patch adds a new backend that emits extended BPF instruction set.
      
      The concept and development are covered by the following articles:
      http://lwn.net/Articles/599755/
      http://lwn.net/Articles/575531/
      http://lwn.net/Articles/603983/
      http://lwn.net/Articles/606089/
      http://lwn.net/Articles/612878/
      
      One of use cases: dtrace/systemtap alternative.
      
      bpf syscall manpage:
      https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b4fc1a460f3017e958e6a8ea560ea0afd91bf6fe
      
      instruction set description and differences vs classic BPF:
      http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/filter.txt
      
      
      
      Short summary of instruction set:
      - 64-bit registers
        R0      - return value from in-kernel function, and exit value for BPF program
        R1 - R5 - arguments from BPF program to in-kernel function
        R6 - R9 - callee saved registers that in-kernel function will preserve
        R10     - read-only frame pointer to access stack
      - two-operand instructions like +, -, *, mov, load/store
      - implicit prologue/epilogue (invisible stack pointer)
      - no floating point, no simd
      
      Short history of extended BPF in kernel:
      interpreter in 3.15, x64 JIT in 3.16, arm64 JIT, verifier, bpf syscall in 3.18, more to come in the future.
      
      It's a very small and simple backend.
      There is no support for global variables, arbitrary function calls, floating point, varargs,
      exceptions, indirect jumps, arbitrary pointer arithmetic, alloca, etc.
      From C front-end point of view it's very restricted. It's done on purpose, since kernel
      rejects all programs that it cannot prove safe. It rejects programs with loops
      and with memory accesses via arbitrary pointers. When kernel accepts the program it is
      guaranteed that program will terminate and will not crash the kernel.
      
      This patch implements all 'must have' bits. There are several things on TODO list,
      so this is not the end of development.
      Most of the code is a boiler plate code, copy-pasted from other backends.
      Only odd things are lack or < and <= instructions, specialized load_byte intrinsics
      and 'compare and goto' as single instruction.
      Current instruction set is fixed, but more instructions can be added in the future.
      
      Signed-off-by: default avatarAlexei Starovoitov <alexei.starovoitov@gmail.com>
      
      Subscribers: majnemer, chandlerc, echristo, joerg, pete, rengolin, kristof.beyls, arsenm, t.p.northover, tstellarAMD, aemerson, llvm-commits
      
      Differential Revision: http://reviews.llvm.org/D6494
      
      llvm-svn: 227008
      e4c8c807
  14. Dec 18, 2014
  15. Dec 12, 2014
  16. Dec 11, 2014
  17. Dec 08, 2014
  18. Sep 12, 2014
  19. Aug 04, 2014
  20. Jul 25, 2014
  21. Jul 17, 2014
  22. Apr 03, 2014
  23. Mar 13, 2014
  24. Feb 18, 2014
  25. Feb 14, 2014
  26. Dec 04, 2013
  27. Nov 28, 2013
  28. Nov 20, 2013
  29. Nov 15, 2013
  30. Nov 13, 2013
  31. Jun 27, 2013
  32. May 08, 2013
  33. Apr 17, 2013
  34. Apr 10, 2013
  35. Mar 18, 2013
  36. Mar 12, 2013
Loading