oprofile
authorRonald G. Minnich <rminnich@google.com>
Fri, 23 May 2014 22:18:18 +0000 (15:18 -0700)
committerRonald G. Minnich <rminnich@google.com>
Fri, 23 May 2014 22:18:18 +0000 (15:18 -0700)
commit718ac565076bd32695df5abf8566b9af90e9c307
tree573bbd708bd62679239efd42135cd95bf0a18aaa
parent94cc807792818749674e27ebd28df17c15640983
oprofile

The oprofile tools are pretty hardwired to a certain directory structure
that is hard to recreate, and not clearly needed.

Change the output of #K/kpoprofile to the following:
PC
bits 63-4, time in ns; 3-0, number PCs following
[an array of PCs]

I don't think we'll miss the 1 ns precision, because there's no way
we're that accurate. +- 16 ns is fine.

TRACEME now calls oprofile_add_backtrace, which adds the backtrace.

Sadly, we're not seeing any backtrace data, but our Go program finds this output
very easy to digest.

Signed-off-by: Ronald G. Minnich <rminnich@google.com>
kern/include/kdebug.h
kern/include/oprofile.h
kern/src/oprofile/cpu_buffer.c