acln0/perf

Issues

• The way forward for the perf package

  #30 opened 4 years ago by ti-mo
  3

• No way to specify PERF_FLAG_FD_OUTPUT (?)

  #28 opened 4 years ago by pwaller
  6

• Revisit testComm waiting on sawcommevfd

  #29 opened 5 years ago by pwaller
  0

• Tests fail as user with paranoid=1

  #15 opened 5 years ago by pwaller
  3

• Failing tests with -test.count=10

  #12 opened 5 years ago by pwaller
  4

• EBADF in testComm

  #24 opened 5 years ago by pwaller
  6

• Samples# dramatically decreases if preciseIP is non-zero.

  #20 opened 5 years ago by pengfei-su
  1

• Missing events due to early return on perfhup

  #23 opened 5 years ago by pwaller
  0

• Other things from `perf list`, e.g. hw_interrupts.received

  #8 opened 5 years ago by pwaller
  5

• Confusing code

  #17 opened 5 years ago by pwaller
  1

• Use Errorf instead of Fatalf in test failures where possible

  #19 opened 5 years ago by acln0
  0

• Idea: perf.Command

  #3 opened 5 years ago by pwaller
  3

• Tracepoint Configurator could be more clever

  #11 opened 5 years ago by acln0
  0

• Should perf.Tracepoint work as part of a group?

  #9 opened 5 years ago by pwaller
  3

• Is CallingThread correctly named?

  #6 opened 5 years ago by pwaller
  2

• (*perf.Group).Options are not respected after g.Add()

  #5 opened 5 years ago by pwaller
  3