1. 11 Jul, 2017 1 commit
    • bveldhoen's avatar
      Add USDT sample (#1229) · b4691fba
      bveldhoen authored
      This sample contains:
          - A library with an operation that uses usdt probes.
          - A console application that calls the operation.
          - Scripts to trace the latency of the operation.
          - Corresponding cmake files.
      b4691fba
  2. 07 Jul, 2017 1 commit
  3. 06 Jul, 2017 1 commit
  4. 01 Jul, 2017 1 commit
  5. 30 Jun, 2017 4 commits
    • Vicent Marti's avatar
      usdt: Use ProcMountNS · 96c1b8e0
      Vicent Marti authored
      96c1b8e0
    • Vicent Marti's avatar
      proc: Enhance bcc_mapping_is_file_backed · 8600ffcb
      Vicent Marti authored
      Cleanup the `strncmp` code and add a few more ignored map names
      8600ffcb
    • Yonghong Song's avatar
      Fix bcc.lua build issue in Ubuntu 17.04 · 08c82535
      Yonghong Song authored
      In fc25 box, gcc6.3.1 is configured with pie default off.
      Here, pie stands for position independent execution.
      
      In ubuntu 17.04, gcc6.3.0, however, is configured with
      pie default on. The gcc driver automatically adds -pie
      to the linker options.
      
      Since bcc.lua build needs pie off, previously, -fno-pie
      is passed to the compiler. -fno-pie is a gcc option
      impacting the code generation and it didn't
      negate the -pie option in the linker. The correct way
      seems to use gcc linker option -no-pie which can
      successfully cancel the default -pie in the linker.
      Signed-off-by: default avatarYonghong Song <yhs@fb.com>
      08c82535
    • Nan Xiao's avatar
      Update LINKS.md · e0d99edf
      Nan Xiao authored
      e0d99edf
  6. 29 Jun, 2017 2 commits
  7. 23 Jun, 2017 1 commit
  8. 22 Jun, 2017 1 commit
  9. 19 Jun, 2017 1 commit
    • Yonghong Song's avatar
      Change clang frontend optimization level from 0 to 2 · 42c00adb
      Yonghong Song authored
      The issue is caused by the following clang change on 5.0:
      https://reviews.llvm.org/D28404
      
      Basically, at -O0, unless always inlining is specified, a
      function will be marked as optnone and noinline.
      
      This causes two kinds of issues: (1). optnone will generate
      suboptimal code with heavy stack use and this high likely can
      cause verifier failure; and (2). even if user mark all his/her
      defined functions in bpf program as always inlining, some
      functions in linux header files are not marked as always inline
      and hence will be marked as noinline instead, ultimately
      causing llvm complaining about global function reference.
      
      This patch bumps the clang optimization level to -O2.
      This should work with older versions of llvm as well.
      Signed-off-by: default avatarYonghong Song <yhs@fb.com>
      42c00adb
  10. 14 Jun, 2017 3 commits
  11. 12 Jun, 2017 1 commit
  12. 10 Jun, 2017 1 commit
    • Carlos Neira's avatar
      fix cc: error: unrecognized command line option -no-pie · 9da21f9e
      Carlos Neira authored
      
      
      cnb@ubuntu-14:~/iovisor/bcc/build$ make
      [  6%] Built target clang_frontend
      [  9%] Built target bpf-static
      [ 16%] Built target bcc-loader-static
      [ 30%] Built target b_frontend
      [ 47%] Built target bcc-static
      [ 48%] Built target CPUDistribution
      [ 50%] Built target FollyRequestContextSwitch
      [ 51%] Built target HelloWorld
      [ 52%] Built target LLCStat
      [ 54%] Built target RandomRead
      [ 55%] Built target RecordMySQLQuery
      [ 56%] Built target TCPSendStack
      [ 80%] Built target bcc-shared
      [ 83%] Built target bpf-shared
      [ 84%] Built target bcc_py
      Linking C executable bcc-lua
      cc: error: unrecognized command line option â-no-pieâ
      make[2]: *** [src/lua/bcc-lua] Error 1
      make[1]: *** [src/lua/CMakeFiles/bcc-lua.dir/all] Error
      
      option is called -fno-pie
      9da21f9e
  13. 08 Jun, 2017 1 commit
  14. 07 Jun, 2017 1 commit
  15. 06 Jun, 2017 3 commits
  16. 05 Jun, 2017 1 commit
  17. 03 Jun, 2017 1 commit
    • Yonghong Song's avatar
      Add a python test for usdt · 505c110a
      Yonghong Song authored
        o The sample application covers different aspects
          of usdt rewriter code generation:
          - const
          - *(ctx + offset)
          - use bpf_probe_read to get trace data
          - the switch in ctx->ip if the same probe
            is triggered in multiple .text locations.
        o folly (https://github.com/facebook/folly/) tracing
          header files are pulled into python test directory and
          used to produce USDT probes.
      Signed-off-by: default avatarYonghong Song <yhs@fb.com>
      505c110a
  18. 01 Jun, 2017 1 commit
  19. 31 May, 2017 5 commits
  20. 30 May, 2017 3 commits
    • Christian Resell's avatar
    • Christian Resell's avatar
    • Yonghong Song's avatar
      Force udst ctx->#reg load to be volatile · b0f891d1
      Yonghong Song authored
      This is related to issue #1133. Compiler sometimes
      generates code patterns likes:
           r1 = ctx + 96
           goto next
         here:
           r1 = ctx + 48
         next:
           r3 = load (r1 + 0)
      Verifier will fail for such cases as r1 is marked
      as "unknown" at the time of load.
      
      The previous workaround is to add volatile attribute
      to the store like
         *(volatile u64 *)&dest = ctx->bx
      The hope is to force ctx related load in-place since
      its value is needed for store.
      
      Unfortunately, this does not always work and compiler
      still has freedom to merge different ctx loads at the
      same time honoring the volatile &dest. In USDT generated
      code, different branches of &dest are the same.
      
      This patch directly make ctx->bx itself as a volatile load:
        *(volatile u64 *)&ctx->bx
      This seems working as compiler stops playing around
      the address pointing to a volatile data.
      Signed-off-by: default avatarYonghong Song <yhs@fb.com>
      b0f891d1
  21. 27 May, 2017 1 commit
  22. 25 May, 2017 3 commits
  23. 24 May, 2017 2 commits