1. 07 Feb, 2017 2 commits
  2. 06 Feb, 2017 2 commits
  3. 05 Feb, 2017 1 commit
  4. 03 Feb, 2017 2 commits
  5. 02 Feb, 2017 1 commit
    • William Cohen's avatar
      Allow RPMS to be built on ppc64 and aarch64 by making luajit optional · ef91b6ed
      William Cohen authored
      Not all architectures have luajit supported.  The bcc configure and
      build were already was set up to make the luajit dependent parts
      optional.  The bcc.spec now makes the luajit dependent parts optional
      too allowing Fedora 25 builds on ppc64, ppc64le, and aarch64.  This
      change has been tested and allows the resulting srpm to build on the
      Fedora koji build system for the newly added architectures.
      Signed-off-by: default avatarWilliam Cohen <wcohen@redhat.com>
      ef91b6ed
  6. 01 Feb, 2017 7 commits
    • 4ast's avatar
      Merge pull request #928 from goldshtn/tp-data-loc · 4a57f4dd
      4ast authored
      Support for __data_loc tracepoint fields
      4a57f4dd
    • Sasha Goldshtein's avatar
      tplist: Don't ignore __data_loc fields · 3ea6eee8
      Sasha Goldshtein authored
      3ea6eee8
    • Sasha Goldshtein's avatar
      c6aaaed1
    • Sasha Goldshtein's avatar
      cc: Support for __data_loc tracepoint fields · b9545a5c
      Sasha Goldshtein authored
      `__data_loc` fields are dynamically sized by the kernel at
      runtime. The field data follows the tracepoint structure entry,
      and needs to be extracted in a special way. The `__data_loc` field
      itself is a 32-bit value that consists of two 16-bit parts: the
      high 16 bits are the length of the data, and the low 16 bits are
      the offset of the data from the beginning of the tracepoint
      structure. From a cursory look, there are >200 tracepoints in
      recent kernels that have this kind of field.
      
      This patch fixes `tp_frontend_action.cc` to recognize and emit
      `__data_loc` fields correctly, as 32-bit opaque fields. Then, it
      introduces two helper macros:
      
      `TP_DATA_LOC_READ(dst, field)` reads from `args->field` by finding
      the right offset and length and emitting the `bpf_probe_read`
      required to fetch the data. This will only work with new kernels.
      
      `TP_DATA_LOC_READ_CONST(dst, field, length)` takes a user-specified
      length rather than finding it from `args->field`. This will work
      on older kernels, where the BPF verifier doesn't allow non-constant
      sizes to be passed to `bpf_probe_read`.
      b9545a5c
    • 4ast's avatar
      Merge pull request #918 from derek0883/mybcc · b77915df
      4ast authored
      Handling multiple concurrent probe users.
      b77915df
    • Derek's avatar
      enum bpf_probe_attach_type to CAPITAL · 227b5b99
      Derek authored
      227b5b99
    • Derek's avatar
      undo rebase · a112514c
      Derek authored
      a112514c
  7. 31 Jan, 2017 10 commits
  8. 30 Jan, 2017 4 commits
  9. 29 Jan, 2017 2 commits
  10. 26 Jan, 2017 1 commit
  11. 24 Jan, 2017 2 commits
  12. 23 Jan, 2017 1 commit
    • Derek's avatar
      Handling multiple concurrent probe users. · 739581f8
      Derek authored
      Event naming pattern changed to $(eventname)_bcc_$(pid)
      Detect /sys/kernel/debug/tracing/instances in bpf_attach_probe,
      if it exist, then will per-instance event, if failed the make global
      event instance as same as before.
      739581f8
  13. 22 Jan, 2017 1 commit
  14. 21 Jan, 2017 2 commits
  15. 20 Jan, 2017 2 commits