Home
last modified time | relevance | path

Searched refs:graph (Results 1 – 19 of 19) sorted by relevance

/system/memory/libmemunreachable/
DTarjan.h72 void Execute(Graph<T>& graph, SCCList<T>& out);
76 void Tarjan(Node<T>* vertex, Graph<T>& graph);
84 void TarjanAlgorithm<T>::Execute(Graph<T>& graph, SCCList<T>& out) { in Execute() argument
88 for (auto& it : graph) { in Execute()
93 for (auto& it : graph) { in Execute()
95 Tarjan(it, graph); in Execute()
102 void TarjanAlgorithm<T>::Tarjan(Node<T>* vertex, Graph<T>& graph) { in Tarjan() argument
111 Tarjan(vertex_next, graph); in Tarjan()
131 void Tarjan(Graph<T>& graph, SCCList<T>& out) { in Tarjan() argument
132 TarjanAlgorithm<T> tarjan{graph.get_allocator()}; in Tarjan()
[all …]
/system/extras/simpleperf/scripts/purgatorio/
DREADME.md8 [Bokeh](https://bokeh.org/) and [D3 flamegraphs](https://github.com/spiermar/d3-flame-graph).
10 …ce, and allow the user to interact with the graph by zooming, hovering on samples and visualize a …
31 …$ adb shell simpleperf record --trace-offcpu --call-graph fp -o /data/local/camera_warm_launch.dat…
47 … the graph. When selecting a et of samples, their aggregated data will be visualized in the other …
49 The toolbox to the right can be used to configure interactions with the graph:
53 ## Flame graph
54 The flame graph is located in the upper right portion. Once samples are selected in the main graph,…
56 ![flame graph](images/flame_graph.png)
60 ![flame graph](images/flame_graph_zoomed.png)
62 …can be done by clicking the related check box. The graph below is the same as in the first flame g…
[all …]
Dpurgatorio.py50 graph = figure(
61 graph.xaxis.formatter = FuncTickFormatter(args={'range': data_range, 'graph': graph}, code="""
78 graph.xaxis.major_label_orientation = math.pi/6
80 graph.circle(y='time',
90 graph.y_range.range_padding = 0
91 graph.xgrid.grid_line_color = None
92 return graph
95 def create_table(graph): argument
100 graph_source = graph.renderers[0].data_source
291 graph = create_graph(args, source, data_range)
[all …]
/system/iorap/docs/binder/
DTaskResult.dot18 * Convert with `graph-easy --as=boxart` to get textual rendering.
26 // graph-easy does not support multiple state syntax {}, write one-by-one
DActivityHint.dot18 * Convert with `graph-easy --as=boxart` to get textual rendering.
/system/extras/simpleperf/doc/
Dinferno.md14 Notice there is no concept of time in a flame graph since all callstack are
72 #### Messy flame graph
73 A healthy flame graph features a single call site at its base (see [here](./report.html)).
Dexecutable_commands_reference.md433 A call graph is a tree showing function call relations. Below is an example.
444 a call graph:
453 A call graph shows how a function calls other functions, and a reversed call graph shows how
454 a function is called by other functions. To show a call graph, we need to first record it, then
457 There are two ways to record a call graph, one is recording a dwarf based call graph, the other is
458 recording a stack frame based call graph. Recording dwarf based call graphs needs support of debug
463 # Record a dwarf based call graph
466 # Record a stack frame based call graph
467 $ simpleperf record -p 11904 --call-graph fp --duration 10
482 previous sample) as the weight of the current sample. As a result, we can get a call graph based
[all …]
Dandroid_application_profiling.md18 - [Record and report call graph](#record-and-report-call-graph)
188 ## Record and report call graph
197 # Record stack frame based call graphs: add "--call-graph fp" in the -r option.
199 -r "-e task-clock:u -f 1000 --duration 10 --call-graph fp" \
266 dwarf-based-call-graph
Dandroid_platform_profiling.md22 # Record surfaceflinger process for 10 seconds with dwarf based call graph. More examples are in
36 $ python app_profiler.py -np surfaceflinger -r "--call-graph fp --duration 10"
Dscripts_reference.md138 # Report call graph
141 # Report call graph in a GUI window implemented by Python Tk.
DREADME.md44 a. When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample
154 better. After all, you can always try dwarf based call graph first, because it always produces
/system/apex/
Dpylintrc393 # Create a graph of every (i.e. internal and external) dependencies in the
395 import-graph=
397 # Create a graph of external dependencies in the given file (report RP0402 must
399 ext-import-graph=
401 # Create a graph of internal dependencies in the given file (report RP0402 must
403 int-import-graph=
/system/tools/mkbootimg/
Dpylintrc386 # Create a graph of every (i.e. internal and external) dependencies in the
388 import-graph=
390 # Create a graph of external dependencies in the given file (report RP0402 must
392 ext-import-graph=
394 # Create a graph of internal dependencies in the given file (report RP0402 must
396 int-import-graph=
/system/update_engine/
Dpylintrc422 # Create a graph of every (i.e. internal and external) dependencies in the
424 import-graph=
426 # Create a graph of external dependencies in the given file (report RP0402 must
428 ext-import-graph=
430 # Create a graph of internal dependencies in the given file (report RP0402 must
432 int-import-graph=
/system/extras/perf2cfg/
DREADME.md3 perf2cfg annotates a control-flow graph (CFG) file with profiling information
/system/chre/pal/doc/
DDoxyfile2131 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2172 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2181 # graph for each documented class showing the direct and indirect implementation
2189 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2205 # class node. If there are many fields or methods and many nodes the graph may
2226 # YES then doxygen will generate a graph for each documented file showing the
2235 # set to YES then doxygen will generate a graph for each documented file showing
2244 # dependency graph for every global function or class method.
2248 # functions only using the \callgraph command. Disabling a call graph can be
2256 # dependency graph for every global function or class method.
[all …]
/system/chre/chre_api/doc/
DDoxyfile2131 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2172 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2181 # graph for each documented class showing the direct and indirect implementation
2189 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2205 # class node. If there are many fields or methods and many nodes the graph may
2226 # YES then doxygen will generate a graph for each documented file showing the
2235 # set to YES then doxygen will generate a graph for each documented file showing
2244 # dependency graph for every global function or class method.
2248 # functions only using the \callgraph command. Disabling a call graph can be
2256 # dependency graph for every global function or class method.
[all …]
/system/media/audio_utils/
DDoxyfile2234 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2275 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2284 # graph for each documented class showing the direct and indirect implementation
2292 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2308 # class node. If there are many fields or methods and many nodes the graph may
2329 # YES then doxygen will generate a graph for each documented file showing the
2338 # set to YES then doxygen will generate a graph for each documented file showing
2347 # dependency graph for every global function or class method.
2351 # functions only using the \callgraph command. Disabling a call graph can be
2359 # dependency graph for every global function or class method.
[all …]
/system/iorap/
DAndroid.bp325 // only the last cc_binary should need the full transitive closure of the dependency graph.
409 // only the last cc_binary should need the full transitive closure of the dependency graph.