Home
last modified time | relevance | path

Searched refs:binaries (Results 1 – 25 of 119) sorted by relevance

12345

/system/extras/simpleperf/scripts/
Dbinary_cache_builder.py49 self.binaries = {}
62 binaries = {}
78 if dso_name not in binaries:
82 binaries[name] = lib.GetBuildIdForPath(dso_name)
83 self.binaries = binaries
99 for binary in self.binaries:
116 expected_build_id = self.binaries.get(binary)
155 for binary in self.binaries:
156 build_id = self.binaries[binary]
/system/sepolicy/private/
Dboringssl_self_test.te1 # System and vendor domains for BoringSSL self test binaries.
11 # to create these marker files, there are dedicated self test binaries which this policy
15 # the system one. To cater for this there are vendor variants of the self test binaries
48 # Allow self test binaries to create/check for the existence of boringssl_self_test_marker files
54 # Allow self test binaries to write their stdout/stderr messages to kmsg_debug
/system/sepolicy/prebuilts/api/31.0/private/
Dboringssl_self_test.te1 # System and vendor domains for BoringSSL self test binaries.
11 # to create these marker files, there are dedicated self test binaries which this policy
15 # the system one. To cater for this there are vendor variants of the self test binaries
48 # Allow self test binaries to create/check for the existence of boringssl_self_test_marker files
54 # Allow self test binaries to write their stdout/stderr messages to kmsg_debug
/system/sepolicy/prebuilts/api/30.0/private/
Dboringssl_self_test.te1 # System and vendor domains for BoringSSL self test binaries.
11 # to create these marker files, there are dedicated self test binaries which this policy
15 # the system one. To cater for this there are vendor variants of the self test binaries
48 # Allow self test binaries to create/check for the existence of boringssl_self_test_marker files
54 # Allow self test binaries to write their stdout/stderr messages to kmsg_debug
Dshell.te35 # Allow shell binaries to write trace data to Perfetto. Used for testing and
41 # Allow shell binaries to exec the perfetto cmdline util and have that
/system/extras/simpleperf/doc/
Dscripts_reference.md105 The binary_cache directory is a directory holding binaries needed by a profiling data file. The
106 binaries are expected to be unstripped, having debug information and symbol tables. The
107 binary_cache directory is used by report scripts to read symbols of binaries. It is also used by
115 binary_cache_builder.py can either pull binaries from an Android device, or find binaries in
119 # Generate binary_cache for perf.data, by pulling binaries from the device.
122 # Generate binary_cache, by pulling binaries from the device and finding binaries in
163 # Adding disassembly for all binaries can cost a lot of time. So we can choose to only add
164 # disassembly for selected binaries.
196 4. Annotated disassembly of that function. It only appears when there are binaries containing that
Dandroid_platform_profiling.md16 on the current main branch. Scripts are in `system/extras/simpleperf/scripts`, binaries are in
31 binaries in `$ANDROID_PRODUCT_OUT/symbols` to report call graphs. However, they are needed to add
38 # Collect unstripped binaries from $ANDROID_PRODUCT_OUT/symbols to binary_cache/.
41 # Report source code and disassembly. Disassembling all binaries is slow, so it's better to add
42 # --binary_filter option to only disassemble selected binaries.
/system/sepolicy/prebuilts/api/28.0/private/
Dshell.te35 # Allow shell binaries to write trace data to Perfetto. Used for testing and
43 # Allow shell binaries to exec the perfetto cmdline util and have that
/system/extras/multinetwork/
DAndroid.bp33 // Sample util binaries.
/system/extras/simpleperf/scripts/test/
Dbinary_cache_builder_test.py42 binary_cache_builder.binaries['simpleperf_runtest_two_functions_arm'] = expected_build_id
62 binary_cache_builder.binaries['elf'] = ''
/system/sepolicy/prebuilts/api/31.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/sepolicy/prebuilts/api/28.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/sepolicy/prebuilts/api/27.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/sepolicy/prebuilts/api/29.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/sepolicy/prebuilts/api/30.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
Dtzdatacheck.te13 # If other users / binaries could modify time zone rules on device this might
/system/sepolicy/prebuilts/api/26.0/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/sepolicy/public/
Dvendor_toolbox.te1 # Toolbox installation for vendor binaries / scripts
/system/apex/tests/testdata/sharedlibs/
DREADME.md4 moving shared libraries used by binaries within an APEX package into another
/system/core/shell_and_utilities/
DAndroid.bp59 // shell and utilities for first stage console. The list of binaries are
/system/extras/simpleperf/demo/
DREADME.md21 ../scripts/ -- contain simpleperf binaries and scripts.
65 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
97 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
129 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
/system/apex/tests/testdata/sharedlibs/build/com.android.apex.test.bar/
DAndroid.bp35 binaries: [ "bar_test" ],
43 binaries: [
/system/sepolicy/prebuilts/api/29.0/private/
Dshell.te35 # Allow shell binaries to write trace data to Perfetto. Used for testing and
43 # Allow shell binaries to exec the perfetto cmdline util and have that
Dapp.te12 # Exception for renderscript binaries (/system/bin/bcc, /system/bin/ld.mc)
/system/apex/tests/testdata/sharedlibs/build/com.android.apex.test.sharedlibs/
DAndroid.bp36 binaries: [ "noop" ],
41 binaries: [

12345