| /system/extras/simpleperf/scripts/ |
| D | binary_cache_builder.py | 70 def collect_binaries(self, binaries: Dict[str, str], binary_cache: BinaryCache):
87 def collect_binaries(self, binaries: Dict[str, str], binary_cache: BinaryCache):
90 for path, build_id in binaries.items():
153 def collect_binaries(self, binaries: Dict[str, str], binary_cache: BinaryCache):
154 self.create_filename_map(binaries)
155 self.create_build_id_map(binaries)
165 def create_filename_map(self, binaries: Dict[str, str]):
168 for path, build_id in binaries.items():
173 def create_build_id_map(self, binaries: Dict[str, str]):
176 for path, build_id in binaries.items():
[all …]
|
| /system/extras/simpleperf/ |
| D | cmd_inject.cpp | 376 std::vector<AutoFDOBinaryInfo> binaries(lbr_data.binaries.size()); in ConvertLBRDataToAutoFDO() local
379 if (sample.binary_id > binaries.size()) { in ConvertLBRDataToAutoFDO()
383 binaries[sample.binary_id - 1].AddAddress(sample.vaddr_in_file); in ConvertLBRDataToAutoFDO()
390 if (branch.from_binary_id > binaries.size()) { in ConvertLBRDataToAutoFDO()
395 binaries[branch.from_binary_id - 1].AddBranch(branch.from_vaddr_in_file, in ConvertLBRDataToAutoFDO()
405 binaries[branch.from_binary_id - 1].AddRange(begin, end); in ConvertLBRDataToAutoFDO()
409 return binaries; in ConvertLBRDataToAutoFDO()
458 std::optional<std::vector<AutoFDOBinaryInfo>> binaries = ConvertLBRDataToAutoFDO(lbr_data_); in PostProcess() local
459 if (!binaries) { in PostProcess()
463 autofdo_binary_map_[dso] = std::move(binaries.value()[binary_id - 1]); in PostProcess()
[all …]
|
| D | branch_list.proto | 72 repeated Binary binaries = 2; field
75 // If binary_id >= 1, it refers to LBRData.binaries[binary_id - 1]. Otherwise, it's invalid.
81 // If from_binary_id >= 1, it refers to LBRData.binaries[from_binary_id - 1]. Otherwise, it's
84 // If to_binary_id >= 1, it refers to LBRData.binaries[to_binary_id - 1]. Otherwise, it's
|
| D | BranchListFile.cpp | 377 for (const BinaryKey& binary : data.binaries) { in LBRDataToString()
433 const auto& binary_proto = lbr_data_proto.binaries(i); in ParseBranchListData()
434 lbr_data.binaries.emplace_back(binary_proto.path(), BuildId(binary_proto.build_id())); in ParseBranchListData()
|
| /system/extras/simpleperf/scripts/test/ |
| D | binary_cache_builder_test.py | 42 binary_cache_builder.binaries['simpleperf_runtest_two_functions_arm'] = build_id
63 binary_cache_builder.binaries['elf'] = ''
85 builder.binaries[filename] = builder.readelf.get_build_id(origin_file)
101 device_path = [p for p in builder.binaries if 'libhello-jni.so' in p][0]
|
| D | tools_test.py | 416 binary_cache_builder.binaries[elf_name] = build_id
419 binary_cache_builder.binaries[filename_without_build_id] = ''
|
| /system/sepolicy/private/ |
| D | boringssl_self_test.te | 1 # 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
|
| D | dexopt_chroot_setup.te | 121 # wrapper that executes other binaries on behalf of dexopt_chroot_setup. Domain
122 # transition will take place as soon as art_exec_exec executes other binaries.
125 # Allow running other binaries in their own domains.
137 # Never allow running other binaries without a domain transition.
|
| D | fsck_untrusted.te | 45 # Only allow entry from vold via fsck binaries
59 # Ignores attempts to access sysfs. fsck binaries seem to like trying to go
|
| D | artd.te | 125 # executes other binaries on behalf of artd. Domain transition will take place
126 # as soon as art_exec_exec executes other binaries.
129 # Allow running other binaries in their own domains.
158 # Allow running other binaries in their own domains.
185 # Never allow running other binaries without a domain transition.
|
| D | simpleperf_boot.te | 23 # Allow simpleperf_boot to read executable binaries.
|
| /system/extras/simpleperf/doc/ |
| D | android_platform_profiling.md | 11 on the current main branch. Scripts are in `system/extras/simpleperf/scripts`, binaries are in
26 binaries in `$ANDROID_PRODUCT_OUT/symbols` to report call graphs. However, they are needed to add
33 # Collect unstripped binaries from $ANDROID_PRODUCT_OUT/symbols to binary_cache/.
36 # Report source code and disassembly. Disassembling all binaries is slow, so it's better to add
37 # --binary_filter option to only disassemble selected binaries.
|
| D | scripts_reference.md | 88 The `binary_cache` directory is a directory holding binaries needed by a profiling data file. The
89 binaries are expected to be unstripped, having debug information and symbol tables. The
90 `binary_cache` directory is used by report scripts to read symbols of binaries. It is also used by
98 `binary_cache_builder.py` can either pull binaries from an Android device, or find binaries in
102 # Generate binary_cache for perf.data, by pulling binaries from the device.
105 # Generate binary_cache, by pulling binaries from the device and finding binaries in
151 # Adding disassembly for all binaries can cost a lot of time. So we can choose to only add
152 # disassembly for selected binaries.
154 # Add disassembly and source code for binaries belonging to an app with package name
187 4. Annotated disassembly of that function. It only appears when there are binaries containing that
|
| D | README.md | 125 1. Needs support of debug information in binaries.
161 2. We need binaries containing DWARF call frame information to unwind stack frames. The binary
192 1. Most C++ code generates binaries containing call frame info, in .eh_frame or .ARM.exidx sections.
197 usually stripped with other debug sections. One way to fix it, is to download unstripped binaries
238 # Collect binaries needed by perf.data in binary_cache/.
326 Most scripts rely on simpleperf binaries to work. To update binaries for scripts (using linux
333 Then you can try the latest simpleperf scripts and binaries in system/extras/simpleperf/scripts.
|
| /system/apex/tests/testdata/vendorapex/ |
| D | Android.bp | 62 binaries: [
127 binaries: [
141 binaries: [
171 binaries: [
293 binaries: [
|
| /system/extras/multinetwork/ |
| D | Android.bp | 26 // Sample util binaries.
|
| /system/sepolicy/public/ |
| D | vendor_toolbox.te | 1 # Toolbox installation for vendor binaries / scripts
|
| /system/extras/simpleperf/demo/ |
| D | README.md | 21 ../scripts/ -- contain simpleperf binaries and scripts.
66 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
98 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
131 # app_profiler.py collects profiling data in perf.data, and binaries on device in binary_cache/.
|
| /system/apex/tests/testdata/sharedlibs/ |
| D | README.md | 4 moving shared libraries used by binaries within an APEX package into another
|
| /system/apex/tests/testdata/sharedlibs/build/com.android.apex.test.sharedlibs/ |
| D | Android.bp | 36 binaries: ["noop"],
41 binaries: [
|
| /system/apex/tests/testdata/sharedlibs/build/com.android.apex.test.bar/ |
| D | Android.bp | 35 binaries: ["bar_test"],
43 binaries: [
|
| /system/core/shell_and_utilities/ |
| D | Android.bp | 62 // shell and utilities for first stage console. The list of binaries are
|
| /system/apex/libs/libapexsupport/tests/ |
| D | Android.bp | 15 binaries: ["libapexsupport-tests"],
|
| /system/apex/docs/ |
| D | howto.md | 29 binaries: ["vold"],
156 `binaries`: installed only for the **_primary_** ABI of the device. In other
170 In order to fine control the ABIs of the native libraries and binaries to be
172 `multilib.[first|lib32|lib64|prefer32|both].[native_shared_libs|binaries]`
176 `binaries`.
192 binaries: ["exec1"], // installed for 64, but not for 32
196 binaries: ["exec2"], // same as binaries without multilib.first
200 binaries: ["exec3"], // installed for 32 and 64
311 ### Linker namespaces for native libraries and binaries
|
| /system/extras/libatrace_rust/benchmark/ |
| D | README.md | 10 There are two binaries implementing the same benchmarks:
30 To run the benchmarks, push the binaries to the device with `adb` and launch them via `adb shell`.
|