graph (reference) in projects: system - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

/system/memory/libmemunreachable/
D	Tarjan.h	72 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/
D	README.md	8 [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 …]
D	purgatorio.py	`51 graph = figure( 62 graph.xaxis.formatter = FuncTickFormatter(args={'range': data_range, 'graph': graph}, code=""" 79 graph.xaxis.major_label_orientation = math.pi/6 81 graph.circle(y='time', 91 graph.y_range.range_padding = 0 92 graph.xgrid.grid_line_color = None 93 return graph 96 def create_table(graph): argument 101 graph_source = graph.renderers[0].data_source 286 graph = create_graph(args, source, data_range) [all …]`
/system/tools/aidl/scripts/
D	vis_aidl_ver_errors.py	`24 graph = [] variable 40 graph += [(last, curr)] 52 G.add_edges_from(graph)`
/system/extras/simpleperf/doc/
D	README.md	32 1) When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample 121 Simpleperf supports two ways recording call stacks with samples. One is DWARF based call graph, 122 the other is stack frame based call graph. Below is their comparison: 124 Recording DWARF based call graph: 132 Recording stack frame based call graph: 144 So if you need to profile code on ARM or profile Java code, DWARF based call graph is better. If you 146 fisrt try DWARF based call graph, which is also the default option when `-g` is used. Because it 148 graph instead. 151 ### Fix broken DWARF based call graph 153 A DWARF-based call graph is generated by unwinding thread stacks. When a sample is recorded, a [all …]
D	inferno.md	`16 Notice there is no concept of time in a flame graph since all callstack are 75 ### Messy flame graph 77 A healthy flame graph features a single call site at its base (see [here](./report.html)).`
D	executable_commands_reference.md	452 A call graph is a tree showing function call relations. Below is an example. 463 a call graph: 472 A call graph shows how a function calls other functions, and a reversed call graph shows how 473 a function is called by other functions. To show a call graph, we need to first record it, then 476 There are two ways to record a call graph, one is recording a dwarf based call graph, the other is 477 recording a stack frame based call graph. Recording dwarf based call graphs needs support of debug 482 # Record a dwarf based call graph 485 # Record a stack frame based call graph 486 $ simpleperf record -p 11904 --call-graph fp --duration 10 670 To report a call graph, please make sure the profiling data is recorded with call graphs,
D	android_platform_profiling.md	`17 # Record surfaceflinger process for 10 seconds with dwarf based call graph. More examples are in 31 $ ./app_profiler.py -np surfaceflinger -r "--call-graph fp --duration 10"`
D	android_application_profiling.md	`172 ## Record and report call graph 181 # Record stack frame based call graphs: add "--call-graph fp" in the -r option. 183 -r "-e task-clock:u -f 1000 --duration 10 --call-graph fp" \ 260 dwarf-based-call-graph`
D	view_the_profile.md	`21 and graph visualisation. 328 # Report call graph.`
D	scripts_reference.md	`126 # Report call graph 129 # Report call graph in a GUI window implemented by Python Tk.`
/system/apex/
D	pylintrc	`393 # 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/
D	pylintrc	`386 # 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/
D	pylintrc	`422 # 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/
D	README.md	`3 perf2cfg annotates a control-flow graph (CFG) file with profiling information`
/system/chre/pal/doc/
D	Doxyfile	2131 # 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/
D	Doxyfile	2131 # 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/
D	Doxyfile	2234 # 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/sepolicy/prebuilts/api/34.0/private/
D	app.te	`362 # Needed for java heap graph ART plugin (perfetto_hprof).`
/system/sepolicy/private/
D	app.te	`362 # Needed for java heap graph ART plugin (perfetto_hprof).`

art
bionic
bootable
build
cts
dalvik
developers
development
device
external
frameworks
hardware
kernel
libcore
libnativehelper
packages
pdk
platform_testing
sdk
system
test
toolchain
tools