Searched refs:how (Results 1 – 25 of 61) sorted by relevance
123
| /system/core/init/ |
| D | service.cpp | 916 void Service::StopOrReset(int how) { in StopOrReset() argument
921 if ((how != SVC_DISABLED) && (how != SVC_RESET) && (how != SVC_RESTART)) { in StopOrReset()
923 LOG(ERROR) << "service '" << name_ << "' requested unknown flag " << how in StopOrReset()
925 how = SVC_DISABLED; in StopOrReset()
929 if (how == SVC_RESET) { in StopOrReset()
932 flags_ |= how; in StopOrReset()
936 if (how == SVC_RESTART) { in StopOrReset()
|
| D | service.h | 166 void StopOrReset(int how);
|
| /system/extras/simpleperf/doc/ |
| D | executable_commands_reference.md | 8 several hardware counters, counting events like how many cpu cycles have happened, how many
9 instructions have executed, or how many cache misses have happened.
17 The stat command gives a summary of how many events have happened in the profiled processes in a
18 time period. Here’s how it works:
23 The record command records samples of the profiled processes in a time period. Here’s how it works:
93 we can select which events to use, which processes/threads to monitor, how long to monitor and the
231 ### Decide how long to stat
233 When monitoring existing threads, we can use --duration to decide how long to monitor. When
249 If you want to write a script to control how long to monitor, you can send one of SIGINT, SIGTERM,
305 option is used, stat cmd outputs an event count for each core. It can be used to see how events
[all …]
|
| D | android_application_profiling.md | 3 This section shows how to profile an Android application.
158 are a lot of unknown symbols in the report, check [here](README.md#how-to-solve-missing-symbols-in-…
296 set how long we want the permission to last.
|
| D | debug_dwarf_unwinding.md | 7 elf files to know how to unwind the stack.
|
| /system/chre/doc/ |
| D | nanoapp_clients.md | 16 how to design a protocol for use with a nanoapp.
48 `createClient()` API supports two modes of operation, which define how events
65 See `host/common/test/chre_test_client.cc` for an example of how to use this
|
| D | nanoapp_overview.md | 101 identical. The key difference is where they are stored and how they are
102 initially loaded into CHRE, and potentially how metadata is handled. In most
133 purposes, as well as to demonstrate how to use the CHRE APIs.
|
| /system/extras/simpleperf/demo/JavaApi/ |
| D | gradle.properties | 5 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/CppApi/ |
| D | gradle.properties | 5 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/SimpleperfExampleCpp/ |
| D | gradle.properties | 5 # For more details on how to configure your build environment visit
|
| /system/extras/libjsonpb/parse/ |
| D | Android.bp | 27 // how to ignore unknown fields yet. Use it only for testing purposes.
|
| /system/teeui/test/example_config/ |
| D | README | 94 more info on how to run atest can be found here: https://source.android.com/compatibility/tests/dev…
98 The following command is how to run the test
|
| /system/extras/simpleperf/demo/SimpleperfExampleKotlin/ |
| D | gradle.properties | 5 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/SimpleperfExampleJava/ |
| D | gradle.properties | 5 # For more details on how to configure your build environment visit
|
| /system/tools/hidl/ |
| D | README.md | 42 of how to generate HIDL makefiles (using the -Landroidbp option).
|
| /system/chre/apps/power_test/common/idl/ |
| D | chre_power_test.fbs | 111 /// The buffer duration is also used as the interval for how often
168 /// See chreWifiNanSubscribeConfig for how to fill in this message.
|
| /system/extras/memory_replay/traces/ |
| D | TRACES | 1 This file describes how the traces were created.
|
| /system/chre/apps/wifi_offload/include/chre/apps/wifi_offload/generated/ |
| 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/tools/aidl/tests/lazy_test/ |
| D | README | 26 an example of how to add a new service. The required files are as follows:
|
| /system/update_engine/update_engine/ |
| D | update_metadata.proto | 119 // Signature message that it knows how to handle. Generally, a client will
120 // only know how to handle one type of signature, but an update may contain
232 // [0, block_size), representing how much should the src_extent shift toward
438 // Information on compressed APEX to figure out how much space is required for
|
| /system/update_engine/ |
| D | update_metadata.proto | 119 // Signature message that it knows how to handle. Generally, a client will
120 // only know how to handle one type of signature, but an update may contain
232 // [0, block_size), representing how much should the src_extent shift toward
438 // Information on compressed APEX to figure out how much space is required for
|
| /system/nfc/src/fuzzers/ |
| D | README.md | 7 with some external dependencies stubbed out. That's how these fuzzers are
|
| /system/sepolicy/private/ |
| D | dex2oat.te | 97 # It would be nice to tie this down, but currently, because of how images are written, we can't
|
| /system/memory/lmkd/ |
| D | README.md | 99 estimating how much data can be swapped. Setting it
|
123