| commit | 677de94066fd9f06fb5fe16a3ef3c3b739df3b82 | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Tue Feb 11 18:23:44 2025 +0000 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Wed Feb 12 11:27:48 2025 +0000 |
| tree | 5e51545456e4eb529df8f930e25cbb62480453a6 | |
| parent | f136935c360cdab478c443bf2ff7181f2b4510c8 [diff] |
pvmfw: Use AVB VM name as DICE component_name The pvmfw-generated DICE node representing the guest kernel (and optional ramdisk) has used the hard-coded component name "vm_entry" since Android 13. Support use-cases where the VM owner wants to set this name by re-using the com.android.virt.name property (currently used to identify a "special" VM) as this CBOR field. Bug: 390527025 Test: atest libpvmfw.dice.test Change-Id: I58337a5bb2b68728a70d0ee5bab2e00ed35a4c1b
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: