Home
last modified time | relevance | path

Searched refs:likely (Results 1 – 25 of 27) sorted by relevance

12

/system/apex/tests/
DREADME.md4 therefore will not likely succeed on a pure AOSP build.
/system/sepolicy/prebuilts/api/26.0/public/
Dupdate_engine_common.te36 # Access is also granted to proc:file, but it is likely unneeded
Ddomain.te529 # services which can change any time framework/core is updated, breakage is likely.
803 # that, even assuming only non-buggy and non-malicious code, it is very likely
/system/libhidl/transport/manager/1.0/
DIServiceManager.hal43 * WARNING: This function is for libhidl/HwBinder use only. You are likely
65 * WARNING: This function is for libhidl/HwBinder use only. You are likely
/system/sepolicy/prebuilts/api/27.0/public/
Dupdate_engine_common.te42 # Access is also granted to proc:file, but it is likely unneeded
Ddomain.te532 # services which can change any time framework/core is updated, breakage is likely.
796 # that, even assuming only non-buggy and non-malicious code, it is very likely
/system/extras/libfec/
Dfec_private.h173 #define likely(x) __builtin_expect(!!(x), 1) macro
Dfec_read.cpp136 if (likely(interleaved < e->start) && !is_zero(f, interleaved)) { in __ecc_read()
332 if (likely(f->hashtree().check_block_hash_with_index(curr, data))) { in verity_read()
/system/chre/doc/
Dframework_testing.md13 platform-specific components likely aren’t compilable/available on a host
Dframework_overview.md112 1. Starting in platform-specific code, likely in a different thread, the
Dporting_guide.md29 words, this code is likely to be re-used by multiple platforms, but it is not
Dnanoapp_developer_guide.md339 Keep in mind that if one nanoapp encounters an assertion failure, it most likely
/system/bpf/bpfloader/
Dbpfloader.rc21 # Enable the eBPF JIT -- but do note that on 64-bit kernels it is likely
/system/extras/simpleperf/doc/
DREADME.md122 3. Old Android versions are likely to be shipped with old kernels (< 3.18),
124 4. Old Android versions are likely to be shipped with Arm32 chips. In Arm32
/system/sepolicy/prebuilts/api/29.0/public/
Dproperty.te132 # likely that the policy is using r_file_perms directly instead of
Ddomain.te654 # services which can change any time framework/core is updated, breakage is likely.
1099 # that, even assuming only non-buggy and non-malicious code, it is very likely
/system/core/libunwindstack/
DAndroidVersions.md83 Since the new ops are not likely to be used very often, this allows
/system/sepolicy/prebuilts/api/30.0/public/
Dproperty.te299 # likely that the policy is using r_file_perms directly instead of
Ddomain.te653 # services which can change any time framework/core is updated, breakage is likely.
1097 # that, even assuming only non-buggy and non-malicious code, it is very likely
/system/sepolicy/public/
Dproperty.te299 # likely that the policy is using r_file_perms directly instead of
Ddomain.te653 # services which can change any time framework/core is updated, breakage is likely.
1097 # that, even assuming only non-buggy and non-malicious code, it is very likely
/system/extras/ioblame/
DREADME85 the app/pid that did the original write (since the write most likely
/system/tools/aidl/docs/
Daidl-cpp.md178 libnativehelper, although this is likely a transitive dependency of the other
/system/core/shell_and_utilities/
DREADME.md29 and how usable it was likely to be.
/system/sepolicy/prebuilts/api/28.0/public/
Ddomain.te648 # services which can change any time framework/core is updated, breakage is likely.
1100 # that, even assuming only non-buggy and non-malicious code, it is very likely

12