| /system/extras/simpleperf/ |
| D | README.md | 112 (PMU). The PMU has several hardware counters, counting events like how many cpu
113 cycles have happened, how many instructions have executed, or how many cache
123 The stat command gives a summary of how many events have happened in the
124 profiled processes in a time period. Here’s how it works:
132 Here’s how it works:
183 processes/threads to monitor, how long to monitor and the print interval.
263 **Decide how long to monitor**
264 When monitoring existing threads, we can use --duration option to decide how long
305 what frequency to dump records, how long to monitor, and where to store records.
348 **Decide how long to monitor**
[all …]
|
| /system/bt/doc/ |
| D | properties.md | 12 ### TODO: write descriptions of what each property means and how
|
| /system/extras/simpleperf/demo/SimpleperfExampleWithNative/ |
| D | gradle.properties | 7 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/SimpleperfExamplePureJava/ |
| D | gradle.properties | 7 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/SimpleperfExampleOfKotlin/ |
| D | gradle.properties | 7 # For more details on how to configure your build environment visit
|
| /system/vold/ |
| D | cryptfs.cpp | 2020 static int cryptfs_enable_all_volumes(struct crypt_mnt_ftr *crypt_ftr, int how, in cryptfs_enable_all_volumes() argument
2035 if (how == CRYPTO_ENABLE_WIPE) { in cryptfs_enable_all_volumes()
2043 } else if (how == CRYPTO_ENABLE_INPLACE) { in cryptfs_enable_all_volumes()
2076 int how = 0; in cryptfs_enable_internal() local
2092 how = CRYPTO_ENABLE_WIPE; in cryptfs_enable_internal()
2094 how = CRYPTO_ENABLE_INPLACE; in cryptfs_enable_internal()
2100 if (how == CRYPTO_ENABLE_INPLACE in cryptfs_enable_internal()
2154 if ((how == CRYPTO_ENABLE_INPLACE) && (!strcmp(key_loc, KEY_IN_FOOTER))) { in cryptfs_enable_internal()
2201 if (how == CRYPTO_ENABLE_INPLACE && !onlyCreateHeader) { in cryptfs_enable_internal()
2288 if (how == CRYPTO_ENABLE_INPLACE && (!no_ui || rebootEncryption)) { in cryptfs_enable_internal()
[all …]
|
| /system/netd/libnetdutils/ |
| D | Syscalls.cpp | 149 Status shutdown(Fd fd, int how) const override { in shutdown()
150 auto rv = ::shutdown(fd.get(), how); in shutdown()
|
| /system/netd/libnetdutils/include/netdutils/ |
| D | MockSyscalls.h | 55 MOCK_CONST_METHOD2(shutdown, Status(Fd fd, int how));
|
| D | Syscalls.h | 70 virtual Status shutdown(Fd fd, int how) const = 0;
|
| /system/core/init/ |
| D | service.cpp | 927 void Service::StopOrReset(int how) { in StopOrReset() argument
932 if ((how != SVC_DISABLED) && (how != SVC_RESET) && (how != SVC_RESTART)) { in StopOrReset()
934 how = SVC_DISABLED; in StopOrReset()
938 if (how == SVC_RESET) { in StopOrReset()
941 flags_ |= how; in StopOrReset()
|
| D | service.h | 119 void StopOrReset(int how);
|
| /system/extras/simpleperf/scripts/ |
| D | app_profiler.config | 47 # You can set how long to profile using "--duration" option, or use Ctrl-C to stop profiling.
|
| /system/extras/tests/sdcard/ |
| D | README | 9 to check how the sdcard scale with the number of processes.
|
| /system/sepolicy/prebuilts/api/26.0/public/ |
| D | dex2oat.te | 57 # It would be nice to tie this down, but currently, because of how images are written, we can't
|
| /system/sepolicy/public/ |
| D | dex2oat.te | 57 # It would be nice to tie this down, but currently, because of how images are written, we can't
|
| /system/chre/apps/wifi_offload/include/chre/apps/wifi_offload/ |
| D | flatbuffers_types.fbs | 65 * Instruction on how to filter scan results before waking up the applications
|
| /system/netd/tests/benchmarks/ |
| D | README.md | 49 label, it might be more useful to log every decile to get a better picture of how spiky
|
| /system/chre/ |
| D | README.md | 26 on the system path of the simulator. Here is an example of how to install it for
137 This project includes a number of nanoapps that serve as both examples of how to
|
| /system/tools/aidl/docs/ |
| D | aidl-cpp.md | 26 This document describes how C++ generation works with attention to:
65 Similar to how Java works, the suffix of the path to a .aidl file must match
|
| /system/update_engine/ |
| D | update_metadata.proto | 105 // Signature message that it knows how to handle. Generally, a client will
106 // only know how to handle one type of signature, but an update may contain
|
| /system/core/shell_and_utilities/ |
| D | README.md | 26 and how usable it was likely to be.
|
| /system/core/liblog/ |
| D | README | 191 indicating how many messages were dropped as a result. Please take
|
| /system/sepolicy/tools/fc_sort/ |
| D | NOTICE | 109 these conditions, and telling the user how to view a copy of this
311 Also add information on how to contact you by electronic and paper mail.
|
| /system/chre/chre_api/doc/ |
| D | Doxyfile | 695 # search path. See also \cite for info how to create references.
893 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
1072 # for information on how to generate the default header that doxygen normally
1083 # footer. See HTML_HEADER for more information on how to generate a default
1085 # section "Doxygen usage" for information on how to generate the default footer
1094 # See also section "Doxygen usage" for information on how to generate the style
1393 # sheet generated by doxygen has an example that shows how to put an image at
1648 # section "Doxygen usage" for information on how to let doxygen write the
1664 # LATEX_HEADER for more information on how to generate a default footer and what
1793 # See also section "Doxygen usage" for information on how to generate the
|
| /system/core/libutils/ |
| D | README | 196 This is similar to how applications are stopped when their packages are
|