Searched +full:early +full:- +full:boot (Results 1 – 25 of 35) sorted by relevance
12
/system/extras/boottime_tools/bootanalyze/ |
D | config.yaml | 4 …system_server: SystemServerTiming(Async)?\s*:\s*(?P<name>\S+) took to complete:\s(?P<time>[0-9]+)ms 5 system_ui: SystemUIBootTiming?\s*:\s*(?P<name>\S+) took to complete:\s(?P<time>[0-9]+)ms 6 fs_shutdown: (?P<name>boot_fs_shutdown),(?P<time>[0-9]+),([0-9]+) 7 ueventd_secs: ueventd:\s(?P<name>\S.+)\stook\s(?P<time>[.0-9]+)\sseconds 8 init_command_ms: init:\sCommand\s(?P<name>\S.+)\sreturned.*took\s(?P<time>[.0-9]+)ms 9 …: init:\sService\s.*exec\s\S+\s\((?P<name>\S.+)\).*pid.*\swaiting\stook\s(?P<time>[.0-9]+)\sseconds 10 zygote64_timing: (?P<name>Zygote64Timing\:\s\S+)\stook\sto\scomplete\:\s(?P<time>[0-9]+)ms 11 zygote32_timing: (?P<name>Zygote32Timing\:\s\S+)\stook\sto\scomplete\:\s(?P<time>[0-9]+)ms 12 …P<component>\S+)\sLong\smonitor\scontention\swith\sowner\s(?P<name>\S.+).*\sfor\s(?P<time>[.0-9]+)s 13 …<component>\S+)\sLong\smonitor\scontention\swith\sowner\s(?P<name>\S.+).*\sfor\s(?P<time>[.0-9]+)ms [all …]
|
/system/core/init/ |
D | README.md | 2 --------------------- 7 All of these are line-oriented, consisting of tokens separated by 8 whitespace. The c-style backslash escapes may be used to insert 11 when it is the last character on a line, may be used for line-folding. 29 -------------- 82 ------- 86 the tail of a to-be-executed queue (unless it is already on the 107 on boot 111 on boot && property:true=true 115 on boot [all …]
|
D | reboot.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 42 #include <android-base/chrono_utils.h> 43 #include <android-base/file.h> 44 #include <android-base/logging.h> 45 #include <android-base/macros.h> 46 #include <android-base/properties.h> 47 #include <android-base/scopeguard.h> 48 #include <android-base/strings.h> 49 #include <android-base/unique_fd.h> 92 if (kDebuggingServices.count(s->name()) && (!only_post_data || s->is_post_data())) { in GetDebuggingServices() [all …]
|
D | init.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 43 #include <android-base/chrono_utils.h> 44 #include <android-base/file.h> 45 #include <android-base/logging.h> 46 #include <android-base/parseint.h> 47 #include <android-base/properties.h> 48 #include <android-base/stringprintf.h> 49 #include <android-base/strings.h> 102 static int signal_fd = -1; 103 static int property_fd = -1; [all …]
|
D | selinux.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 17 // This file contains the functions that initialize SELinux during boot as well as helper functions 26 // The monolithic policy variant is for legacy non-treble devices that contain a single SEPolicy 54 #include <android/api-level.h> 62 #include <android-base/chrono_utils.h> 63 #include <android-base/file.h> 64 #include <android-base/logging.h> 65 #include <android-base/parseint.h> 66 #include <android-base/strings.h> 67 #include <android-base/unique_fd.h> [all …]
|
/system/bpf/bpfloader/ |
D | bpfloader.rc | 1 # zygote-start is what officially starts netd (see //system/core/rootdir/init.rc) 2 # However, on some hardware it's started from post-fs-data as well, which is just 7 # - /sys/fs/bpf is already mounted, 8 # - apex (incl. rollback) is initialized (so that in the future we can load bpf 10 # - system properties have been set, this is because isBpfSupported() calls 13 # - logd is ready for us to log stuff 15 # At the same time we want to be as early as possible to reduce races and thus 17 # stuff) and we absolutely want to be before netd and the system boot slot is 21 # Enable the eBPF JIT -- but do note that on 64-bit kernels it is likely 35 # However, while the rlimit is per-thread, the accounting is system wide. [all …]
|
/system/core/rootdir/ |
D | init.rc | 14 # Cgroups are mounted right before early-init using list from /etc/cgroups.json 15 on early-init 44 # set RLIMIT_NICE to allow priorities from 19 to -20 54 # Disable dm-verity hash prefetching, since it doesn't help performance 58 # Generate ld.config.txt for early executed processes 59 exec -- /system/bin/linkerconfig --target /linkerconfig/bootstrap 69 # Run apexd-bootstrap so that APEXes that provide critical libraries 72 exec_start apexd-bootstrap 90 on early-init && property:ro.product.cpu.abilist32=* 92 on early-init && property:ro.product.cpu.abilist64=* [all …]
|
D | init.usb.rc | 6 on post-fs-data 15 service adbd /system/bin/adbd --root_seclabel=u:r:su:s0 22 # Set default value on sys.usb.configfs early in boot sequence. It will be 23 # overridden in `on boot` action of init.hardware.rc. 103 # Used to set USB configuration at boot and to switch the configuration 105 on boot && property:persist.sys.usb.config=* 139 on userspace-reboot-requested
|
/system/vold/ |
D | Keymaster.h | 8 * http://www.apache.org/licenses/LICENSE-2.0 26 #include <android-base/macros.h> 37 // Surprisingly -- to me, at least -- this is totally fine. You can re-define symbols that were 67 if (output) output->clear(); in updateCompletely() 117 // Exports a keymaster key with STORAGE_KEY tag wrapped with a per-boot ephemeral key 124 // Begin a new cryptographic operation, collecting output parameters if pointer is non-null 131 // Tell all Keymaster instances that early boot has ended and early boot-only keys can no longer 159 error = -1, 160 upgrade = -2,
|
D | MetadataCrypt.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 30 #include <android-base/file.h> 31 #include <android-base/logging.h> 32 #include <android-base/properties.h> 33 #include <android-base/strings.h> 34 #include <android-base/unique_fd.h> 62 bool set_dun = true; // Non-legacy driver always sets DUN 79 CryptoType().set_config_name("aes-256-xts").set_kernel_name("AES-256-XTS").set_keysize(64); 90 // We're about to mount data not verified by verified boot. Tell Keymaster instances that early in mount_via_fs_mgr() 91 // boot has ended. in mount_via_fs_mgr() [all …]
|
D | Keymaster.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 19 #include <android-base/logging.h> 31 if (mDevice) mDevice->abort(mOpHandle); in ~KeymasterOperation() 49 size_t toRead = static_cast<size_t>(inputLen - inputConsumed); in updateCompletely() 52 auto error = mDevice->update(mOpHandle, hidl_vec<km::KeyParameter>(), inputBlob, in updateCompletely() 79 if (output) output->assign(reinterpret_cast<const char*>(&_output[0]), _output.size()); in finish() 81 auto error = mDevice->finish(mOpHandle, hidl_vec<km::KeyParameter>(), hidl_vec<uint8_t>(), in finish() 108 if (dev->halVersion().securityLevel != SecurityLevel::STRONGBOX) { in Keymaster() 114 auto& version = mDevice->halVersion(); in Keymaster() 117 << ", HAL: " << mDevice->descriptor() << "/" << mDevice->instanceName(); in Keymaster() [all …]
|
/system/keymaster/include/keymaster/ |
D | keymaster_enforcement.h | 8 * http://www.apache.org/licenses/LICENSE-2.0 95 // The time-related methods address the fact that different enforcement contexts may have 96 // different time-related capabilities. In particular: 98 // - They may or may not be able to check dates against real-world clocks. 100 // - They may or may not be able to check timestampls against authentication trustlets (minters 103 // - They must have some time source for relative times, but may not be able to provide more 130 * this method. On non-Linux POSIX systems, CLOCK_MONOTONIC is good, assuming the device does 136 * Get whether or not we're in early boot. See early_boot_ended() below. 188 * Inform the KeymasterEnforcement object that early boot stage has ended.
|
/system/sepolicy/private/ |
D | boringssl_self_test.te | 5 # per device boot, also run a series of Known Answer Tests (KAT) to verify functionality. 12 # gives access to and which are run during early-init. 62 -vendor_boringssl_self_test 63 -boringssl_self_test 64 -init 65 -vendor_init 70 -vendor_boringssl_self_test 71 -boringssl_self_test 72 -init 73 -vendor_init
|
/system/sepolicy/prebuilts/api/30.0/private/ |
D | boringssl_self_test.te | 5 # per device boot, also run a series of Known Answer Tests (KAT) to verify functionality. 12 # gives access to and which are run during early-init. 62 -vendor_boringssl_self_test 63 -boringssl_self_test 64 -init 65 -vendor_init 70 -vendor_boringssl_self_test 71 -boringssl_self_test 72 -init 73 -vendor_init
|
/system/core/fs_mgr/ |
D | README.overlayfs.md | 5 ------------ 8 system partition as read-write and then add or modify any number of files 11 Limited memory systems use read-only types of file systems or logical resizable 13 right-sized, and have been deduped at the block level to compress the content. 17 OverlayFS resolves these debug scenarios with the _adb disable-verity_ and 22 -------------------- 27 $ adb disable-verity 29 $ adb wait-for-device 47 $ adb disable-verity 52 $ adb remount -R [all …]
|
/system/apex/docs/ |
D | README.md | 4 that is used in the install flow for lower-level system 8 ([HALs](/https://source.android.com/devices/architecture/hal-types)), runtime 17 the Google Play Store app), using a similar model for lower-level OS components 20 - APK-based modules can't be used early in the boot sequence. The package 23 the boot procedure. 24 - The APK format (particularly the manifest) is designed for Android apps and 29 This section describes the high-level design of the APEX file format and the 36 ![APEX file format](apex-format.png) 45 - `apex_manifest.json` 46 - `AndroidManifest.xml` [all …]
|
/system/sepolicy/prebuilts/api/28.0/public/ |
D | init.te | 27 # /dev/event-log-tags 34 # /dev/device-mapper, /dev/block(/.*)? 40 # restorecon for early mount device symlinks 80 # Mount on /dev/usb-ffs/adb. 121 # This can be done in device-specific policy via type or typeattribute 127 # Allow read-only access to context= mounted filesystems. 138 # init.<board>.rc files often include device-specific types, so 144 -app_data_file 145 -exec_type 146 -misc_logd_file [all …]
|
/system/sepolicy/prebuilts/api/27.0/public/ |
D | init.te | 24 # /dev/event-log-tags 31 # /dev/device-mapper, /dev/block(/.*)? 37 # restorecon for early mount device symlinks 69 # Mount on /dev/usb-ffs/adb. 107 # This can be done in device-specific policy via type or typeattribute 113 # Allow read-only access to context= mounted filesystems. 124 # init.<board>.rc files often include device-specific types, so 130 -app_data_file 131 -exec_type 132 -misc_logd_file [all …]
|
/system/sepolicy/prebuilts/api/26.0/public/ |
D | init.te | 20 # /dev/event-log-tags 27 # /dev/device-mapper, /dev/block(/.*)? 33 # restorecon for early mount device symlinks 65 # Mount on /dev/usb-ffs/adb. 102 # This can be done in device-specific policy via type or typeattribute 108 # Allow read-only access to context= mounted filesystems. 119 # init.<board>.rc files often include device-specific types, so 125 -app_data_file 126 -exec_type 127 -misc_logd_file [all …]
|
/system/sepolicy/public/ |
D | init.te | 26 # /dev/event-log-tags 35 # /dev/device-mapper, /dev/block(/.*)? 41 # restorecon for early mount device symlinks 53 # Create /mnt/sdcard -> /storage/self/primary symlink. 104 # Mount on /dev/usb-ffs/adb. 110 # Bind-mount on /system/apex/com.android.art 154 # This can be done in device-specific policy via type or typeattribute 160 # Allow read-only access to context= mounted filesystems. 171 # init.<board>.rc files often include device-specific types, so 177 -app_data_file [all …]
|
/system/sepolicy/prebuilts/api/30.0/public/ |
D | init.te | 26 # /dev/event-log-tags 35 # /dev/device-mapper, /dev/block(/.*)? 41 # restorecon for early mount device symlinks 53 # Create /mnt/sdcard -> /storage/self/primary symlink. 104 # Mount on /dev/usb-ffs/adb. 110 # Bind-mount on /system/apex/com.android.art 154 # This can be done in device-specific policy via type or typeattribute 160 # Allow read-only access to context= mounted filesystems. 171 # init.<board>.rc files often include device-specific types, so 177 -app_data_file [all …]
|
/system/sepolicy/prebuilts/api/29.0/public/ |
D | init.te | 26 # /dev/event-log-tags 33 # /dev/device-mapper, /dev/block(/.*)? 39 # restorecon for early mount device symlinks 84 # Mount on /dev/usb-ffs/adb. 131 # This can be done in device-specific policy via type or typeattribute 137 # Allow read-only access to context= mounted filesystems. 148 # init.<board>.rc files often include device-specific types, so 154 -app_data_file 155 -exec_type 156 -misc_logd_file [all …]
|
/system/core/bootstat/ |
D | bootstat.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 17 // The bootstat command provides options to persist boot events with the current 40 #include <android-base/chrono_utils.h> 41 #include <android-base/file.h> 42 #include <android-base/logging.h> 43 #include <android-base/parseint.h> 44 #include <android-base/properties.h> 45 #include <android-base/strings.h> 155 // Scans the boot event record store for record files and logs each boot event 165 if (info->second.atom == android::util::BOOT_TIME_EVENT_ERROR_CODE_REPORTED) { in LogBootEvents() [all …]
|
/system/timezone/tzdatacheck/ |
D | tzdatacheck.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0 31 #include "android-base/logging.h" 62 // Version bytes are: AAA.BBB|CCCCC - the format version is AAA.BBB 66 // Version bytes are: AAA.BBB|CCCCC - the format major version is AAA 69 // Version bytes are: AAA.BBB|CCCCC - the format major version is AAA 72 // Version bytes are: AAA.BBB|CCCCC - the format major version is AAA 75 // Version bytes are: AAA.BBB|CCCCC - the format minor version is BBB 78 // Version bytes are: AAA.BBB|CCCCC - the IANA rules version is CCCCC 82 // Version bytes are: AAA.BBB|CCCCC - the rules version is CCCCC 249 // Create an empty directory with the temporary name. For this we need a non-const char*. in deleteDir() [all …]
|
/system/update_engine/ |
D | README.md | 6 called A/B updates, over-the-air ([OTA]) updates, seamless updates, or simply 14 non-usable state. And reducing the need for flashing devices manually or at 26 * If the update applies correctly but fails to boot, the system will rollback 39 which copy has the higher priority at boot time) and when a new update is 89 After the inactive partition is updated, the entire partition is re-read, hashed 94 reconstructs the dm-verity tree hash of the ROOT partition and writes it at the 107 higher priority (on a boot, a partition with higher priority is booted 108 first). Once the user reboots the system, it will boot into the updated 110 updater client calls into the [`chromeos-setgoodkernel`] program. The program 111 verifies the integrity of the system partitions using the dm-verity and marks [all …]
|
12