Searched refs:how (Results 1 – 25 of 74) sorted by relevance
123
| /system/core/init/ |
| D | service.cpp | 703 void Service::StopOrReset(int how) { in StopOrReset() argument
708 if ((how != SVC_DISABLED) && (how != SVC_RESET) && (how != SVC_RESTART)) { in StopOrReset()
710 how = SVC_DISABLED; in StopOrReset()
714 if (how == SVC_RESET) { in StopOrReset()
717 flags_ |= how; in StopOrReset()
721 if (how == SVC_RESTART) { in StopOrReset()
|
| D | service.h | 144 void StopOrReset(int how);
|
| /system/extras/simpleperf/doc/ |
| D | executable_commands_reference.md | 7 - [How simpleperf works](#how-simpleperf-works)
13 - [Decide how long to stat](#decide-how-long-to-stat)
22 - [Decide how long to record](#decide-how-long-to-record)
37 several hardware counters, counting events like how many cpu cycles have happened, how many
38 instructions have executed, or how many cache misses have happened.
46 The stat command gives a summary of how many events have happened in the profiled processes in a
47 time period. Here’s how it works:
52 The record command records samples of the profiled processes in a time period. Here’s how it works:
122 we can select which events to use, which processes/threads to monitor, how long to monitor and the
221 ### Decide how long to stat
[all …]
|
| /system/bt/doc/ |
| D | properties.md | 12 ### TODO: write descriptions of what each property means and how
|
| /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/SimpleperfExamplePureJava/ |
| D | gradle.properties | 7 # 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/SimpleperfExampleWithNative/ |
| D | gradle.properties | 7 # For more details on how to configure your build environment visit
|
| /system/extras/simpleperf/demo/JavaApi/ |
| D | gradle.properties | 5 # 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/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 | 91 more info on how to run atest can be found here: https://source.android.com/compatibility/tests/dev…
95 The following command is how to run the test
|
| /system/netd/libnetdutils/ |
| D | Syscalls.cpp | 174 Status shutdown(Fd fd, int how) const override { in shutdown()
175 auto rv = ::shutdown(fd.get(), how); in shutdown()
|
| /system/netd/libnetdutils/include/netdutils/ |
| D | MockSyscalls.h | 60 MOCK_CONST_METHOD2(shutdown, Status(Fd fd, int how));
|
| /system/tools/hidl/ |
| D | README.md | 42 of how to generate HIDL makefiles (using the -Landroidbp option).
|
| /system/bt/gd/l2cap/classic/ |
| D | facade.proto | 22 // Get the buffer size of channel queue end for L2CAP user (how many packets we can buffer
|
| /system/sepolicy/prebuilts/api/27.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/prebuilts/api/28.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/extras/memory_replay/traces/ |
| D | TRACES | 1 This file describes how the traces were created.
|
| /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/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/bt/gd/docs/testing/ |
| D | cert_test.md | 28 diagram shows how the system could be configured:
65 should have no knowledge of how this component works * **Root-Canal**: A
191 Logs are produced and saved whenever GD cert tests runs. Depending on how the
|
| /system/tools/aidl/tests/lazy_test/ |
| D | README | 26 an example of how to add a new service. The required files are as follows:
|
123