Searched refs:callstack (Results 1 – 3 of 3) sorted by relevance
| /system/extras/simpleperf/scripts/ |
| D | report_html.py | 156 def add_callstack(self, event_count, callstack, build_addr_hit_map): argument
160 for i, (lib_id, func_id, addr) in enumerate(callstack):
180 for item in reversed(callstack):
184 for item in callstack:
614 callstack = [(lib_id, func_id, symbol.vaddr_in_file)]
619 callstack.append((lib_id, func_id, symbol.vaddr_in_file))
620 if len(callstack) > MAX_CALLSTACK_LENGTH:
621 callstack = callstack[:MAX_CALLSTACK_LENGTH]
622 thread.add_callstack(raw_sample.period, callstack, self.build_addr_hit_map)
|
| /system/extras/simpleperf/doc/ |
| D | inferno.md | 14 Notice there is no concept of time in a flame graph since all callstack are
42 Inferno relies on simpleperf to record the callstack of a native application
77 callstack are impossible to merge properly. By default Inferno asks
|
| D | executable_commands_reference.md | 480 so we know the callstack of a thread when it is scheduled out. And when reporting a perf.data
|