Lines Matching refs:is

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
6 # It is important that we start bpfloader after:
7 #   - /sys/fs/bpf is already mounted,
8 #   - apex (incl. rollback) is initialized (so that in the future we can load bpf
10 #   - logd is ready for us to log stuff
13 # failures (before memory is fragmented, and cpu is busy running tons of other
14 # stuff) and we absolutely want to be before netd and the system boot slot is
18     # Enable the eBPF JIT -- but do note that on 64-bit kernels it is likely
32     # However, while the rlimit is per-thread, the accounting is system wide.
35     # if its memlock rlimit is only 8MiB - since there would be none left for it.
37     # bpfloader succeeding is critical to system health, since a failure will
39     # recovery is a full kernel reboot.
47     # But we don't know what that is for all possible devices...
51     # capability is not even checked by the kernel's bpf system call.