Lines Matching refs:stack

28    1) When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample
39    4) It uses the standard Android stack unwinder, so its results are consistent with all other
113    mode, recording stack frame based call graphs doesn't work well.
117 Below is our experiences of dwarf based call graphs and stack frame based call graphs.
122 3. Can only unwind 64K stack for each sample. So usually can't show complete flamegraph. But
124 4. Take more CPU time than stack frame based call graphs. So the sample frequency is suggested
127 stack frame based call graphs:
128 1. Need support of stack frame registers.
130    stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.
132    reserve stack frame registers.
139 may be better. If you need to profile C++ code on ARM64, stack frame based call graphs may be
142 try stack frame based call graphs instead.
150 64KB stack data is dumped by the kernel. By unwinding the stack based on dwarf information, we get
151 a callchain. But the thread stack can be much longer than 64KB. In that case, we can't unwind to