Android init介紹(下)

上一篇: <Android init介紹(上)>

5. AIL

在init啟動過程中，系統服務等均是通過解析rc文件來啟動，而rc文件則是由Android初始化語言(Android Init Language)的腳本寫成

5.1 格式介紹

AIL以Section為區分，由如下import、action和service三類Section

5.1.1 import section

主要用於導入其他rc文件

import <path>

上面的命令將導入path指定的文件然后被解析為action和service

5.1.2 action section

action section由trigger和一些command組成
以on開頭，trigger是判斷條件，command是具體執行一些操作；當滿足trigger條件時，執行這些command

格式如下

on <trigger> [&& <trigger>]*
   <command>
   <command>
   <command>

trigger的內容包含如下

/* 
 * 事件觸發器
 * -- 表示當trigger early或QueueEventTrigger("early")調用時觸發
 */
on early

/* 
 * 屬性觸發器
 * -- 表示當sys.boot_from_charger_mode的值通過property_set設置為1時觸發
 */
on property:sys.boot_from_charger_mode=1

/*
 * 多個條件用&&連接
 * -- 表示當zygote-start觸發並且ro.crypto.state屬性值為unencrypted時觸發
on zygote-start && property:ro.crypto.state=unencrypted

command就是一些具體的操作，由BuiltinFunctionMap::Map(builtin_functions)定義來執行特定的操作

    // 終止charger服務
    class_stop charger
    // 開啟watchdogd服務
    start watchdogd
    // 觸發late-init
    trigger late-init

5.1.3 service section

service section由service加上一些option組成
以service開頭，name是為服務名稱，pathname為服務的執行文件路徑，argument表示執行文件帶的參數，option表示這個服務的一些配置，option由OptionParserMap::Map(option_parsers)定義

service <name> <pathname> [ <argument> ]*
   <option>
   <option>
   ...

5.2 文件解析

/*
 * 初始化Subcontext
 */
InitializeSubcontexts()
    SelinuxHasVendorInit()
        Subcontext::Subcontext()
            Subcontext::Fork()
                fork()
                execv("/init", {"/init", "subcontext", "u:r:vendor_init:s0", fd, nullptr})

// 創建ActionManager實例
ActionManager::GetInstance()
// 創建ServiceList實例
ServiceList::GetInstance()

LoadBootScripts()
    CreateParser(ActionManager, ServiceList)
    Parser::ParseConfig("/init.rc")
    Parser::ParseConfig("/system/etc/init")
    Parser::ParseConfig("/vendor/etc/init")
        Parser::ParseConfigFile()
            Parser::ParseData()

可以看出rc文件文件主要位於[/]、[/system/etc/init/]、[/vendor/etc/init/]

# tree /
.
+--- init.environ.rc
+--- init.rc
+--- init.recovery.hardware.rc
+--- init.usb.configfs.rc
+--- init.usb.rc
+--- init.zygote32.rc
+--- init.zygote64_32.rc

# tree /system/etc/init/
.
+--- [e-mail]
+--- atrace.rc
+--- atrace_userdebug.rc
+--- audioserver.rc
+--- blank_screen.rc
+--- bootanim.rc
+--- bootstat-debug.rc
+--- bootstat.rc
+--- cameraserver.rc
+--- com.android.car.powertestservice.rc
+--- com.android.car.procfsinspector.rc
+--- drmserver.rc
+--- dumpstate.rc
+--- gatekeeperd.rc
+--- gsi
|   +--- init.vndk-27.rc
+--- hwservicemanager.rc
+--- incidentd.rc
+--- init-debug.rc
+--- init.gsi.rc
+--- installd.rc
+--- keystore.rc
+--- lmkd.rc
+--- logcatd.rc
+--- logd.rc
+--- logtagd.rc
+--- mdnsd.rc
+--- mediadrmserver.rc
+--- mediaextractor.rc
+--- mediametrics.rc
+--- mediaserver.rc
+--- mtpd.rc
+--- netd.rc
+--- perfetto.rc
+--- perfprofd.rc
+--- racoon.rc
+--- recovery-persist.rc
+--- recovery-refresh.rc
+--- servicemanager.rc
+--- statsd.rc
+--- storaged.rc
+--- surfaceflinger.rc
+--- thermalservice.rc
+--- tombstoned.rc
+--- uncrypt.rc
+--- update_engine.rc
+--- update_verifier.rc
+--- usbd.rc
+--- vdc.rc
+--- vold.rc
+--- vr_hwc.rc
+--- wait_for_keymaster.rc
+--- wifi-events.rc
+--- wificond.rc

# tree /vendor/etc/init/
.
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- android.hardware.health@2.0-service.`hardware`.rc
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- [e-mail]
+--- android.hardware.thermal@1.1-service.`hardware`.rc
+--- [e-mail]
+--- [e-mail]
+--- daemon_cl.rc
+--- hostapd.android.rc
+--- host_server.rc
+--- hw
|   +--- init.coredump.rc
|   +--- init.crashlogd.rc
|   +--- init.dvc_desc.rc
|   +--- init.`hardware`.rc
|   +--- init.kernel.rc
|   +--- init.logs.rc
|   +--- init.npk.rc
+--- name_server.rc
+--- rild.rc
+--- SampleDriverAll.rc
+--- vndservicemanager.rc

5.3 事件觸發

/*
 * am為ActionManager::GetInstance()
 * QueueEventTrigger構造了一個EventTrigger對象, 放到事件隊列中
 * !!!注意此處並沒有觸發
 */ 
am.QueueEventTrigger("early-init");
am.QueueEventTrigger("init");
am.QueueEventTrigger("late-init");

/*
 * QueueBuiltinAction構造了一個Action對象, 放到事件隊列和動作隊列中
 * !!!注意此處並沒有觸發
 */ 
am.QueueBuiltinAction(wait_for_coldboot_done_action,  "wait_for_coldboot_done");
am.QueueBuiltinAction(MixHwrngIntoLinuxRngAction,     "MixHwrngIntoLinuxRng");
am.QueueBuiltinAction(SetMmapRndBitsAction,           "SetMmapRndBits");
am.QueueBuiltinAction(SetKptrRestrictAction,          "SetKptrRestrict");
am.QueueBuiltinAction(keychord_init_action,           "keychord_init");
am.QueueBuiltinAction(console_init_action,            "console_init");
am.QueueBuiltinAction(MixHwrngIntoLinuxRngAction,     "MixHwrngIntoLinuxRng");
am.QueueBuiltinAction(queue_property_triggers_action, "queue_property_triggers");

while (true) {
    ...
    if (!(waiting_for_prop || Service::is_exec_service_running())) {
        // 依次觸發early-init、init、late-init的命令
        am.ExecuteOneCommand();
    }
    ...
}

5.4 詳細過程

Android啟動過程中重要的trigger事件如下

- early-init
  +--- start ueventd
- init
- charger                   /* 當ro.bootmode為charger執行 */
- late-init
  +--- early-fs
  +--- fs                   /* 掛載系統分區 */
     +--- mount_all /vendor/etc/fstab.${ro.hardware}
  +--- post-fs              /* 執行依賴文件系統的命令 */
     +--- load_system_props
        +--- load_properties_from_file("/system/build.prop", NULL);
        +--- load_properties_from_file("/odm/build.prop", NULL);
        +--- load_properties_from_file("/vendor/build.prop", NULL);
        +--- load_properties_from_file("/factory/factory.prop", "ro.*");
        +--- load_recovery_id_prop();
     +--- start logd
     +--- start servicemanager
     +--- start hwservicemanager
     +--- start vndservicemanager
  +--- late-fs
     +--- class_start early_hal
  +--- post-fs-data         /* data分區初始化 */
     +--- start vold
     +--- installkey /data
     +--- bootchart start
     +--- init_user0
  +--- zygote-start
     +--- exec_start update_verifier_nonencrypted
     +--- start netd
     +--- start zygote
     +--- start zygote_secondary
  +--- load_persist_props_action
     +--- load_persist_props
     +--- LoadPersistentProperties()
     +--- start logd
     +--- start logd-reinit
  +--- firmware_mounts_complete
     +--- rm /dev/.booting
  +--- early-boot
  +--- boot

  +--- property:sys.boot_completed=1
     +--- bootchart stop

參考:
<Android系統啟動流程>
<Android 9.0 init進程分析>
<Android 8.1 啟動篇(一) -- 深入研究 init>