668224f6a1
error: this `impl` can be derived
--> packages/modules/Virtualization/microdroid/payload/config/src/lib.rs:90:1
|
90 | / impl Default for TaskType {
91 | | fn default() -> TaskType {
92 | | TaskType::Executable
93 | | }
94 | | }
| |_^
bug: 270756468
Test: test_compiler.py
Change-Id: Ibad99d63b88efa8a20e6f618abe7b86159139234
|
||
|---|---|---|
| .. | ||
| config | ||
| include/microdroid | ||
| metadata | ||
| src/com/android/virt | ||
| Android.bp | ||
| README.md | ||
| metadata.cc | ||
| metadata.proto | ||
| mk_payload.cc | ||
README.md
Microdroid Payload
Payload disk is a composite disk image referencing host APEXes and an APK so that microdroid mounts/activates APK/APEXes and executes a binary within the APK.
Payload disk is created by VirtualizationService Service when starting a VM.
Partitions
Payload disk has 1 + N(number of APEX/APK payloads) partitions.
The first partition is a "payload-metadata" partition which describes other partitions. And APEXes and an APK are following as separate partitions.
For now, the order of partitions are important.
- partition 1: Metadata partition
- partition 2 ~ n: APEX payloads
- partition n+1, n+2: APK payload and its idsig
It's subject to change in the future, though.
Metadata partition
Metadata partition provides description of the other partitions and the location for VM payload configuration.
The partition is a protobuf message prefixed with the size of the message.
| offset | size | description |
|---|---|---|
| 0 | 4 | Header. unsigned int32: body length(L) in big endian |
| 4 | L | Body. A protobuf message. schema |
Payload partitions
Each payload partition presents APEX or APK passed from the host.
The size of a payload partition must be a multiple of 4096 bytes.