Lines Matching refs:stack

43    a. When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample
54    d. It uses the standard Android stack unwinder, so its results are consistent with all other
125 mode, recording stack frame based call graphs doesn't work well.
130 Below is our experiences of dwarf based call graphs and stack frame based call graphs.
135 3. Can only unwind 64K stack for each sample. So usually can't show complete flamegraph. But
137 4. Take more CPU time than stack frame based call graphs. So the sample frequency is suggested
140 stack frame based call graphs:
141 1. Need support of stack frame registers.
143    stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.
145    reserve stack frame registers.
152 may be better. If you need to profile C++ code on ARM64, stack frame based call graphs may be
155 try stack frame based call graphs instead.