diff options
| author | Andy McFadden <fadden@android.com> | 2010-08-25 12:05:44 -0700 |
|---|---|---|
| committer | Andy McFadden <fadden@android.com> | 2010-08-25 14:55:19 -0700 |
| commit | fe1d6d586614fa51d82857e09128d6671be21d56 (patch) | |
| tree | ca47b8e3b43d9914f9cc14c8836cf22d095c72ab /vm/compiler/codegen/arm/CodegenDriver.c | |
| parent | 9e02e4b1fa08cebefa0f79cd407f4a88611cf473 (diff) | |
Add option for specifying wall-clock in method profiling.
Normally you want to use the per-thread CPU clock rather than the wall
clock, because (a) it's more useful and (b) traceview goes a little nuts
if you don't. However, it's useful for some performance testing.
The command-line option allows you to switch modes like this:
% adb shell stop
% adb shell setprop dalvik.vm.extra-opts -Xprofile:wallclock
% adb shell start
This also changes the somewhat nebulous "clock=global" trace header line
to "clock=wall". Nothing looks at this anyway so I'm not worried
about breaking compatibility.
While I was in here, I fixed a couple of problems caused by failure to
initialize data structures that made dmtracedump crash (yay valgrind).
Bug 2943229.
(cherry-pick from dalvik-dev)
Change-Id: I2f6657f7abe02f2a17784588d922b88397639a47
Diffstat (limited to 'vm/compiler/codegen/arm/CodegenDriver.c')
0 files changed, 0 insertions, 0 deletions
