| commit | ba666feb01d5b32756dd1674757142bd23ab523f | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Tue Nov 19 16:44:33 2024 +0000 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Thu Jan 16 19:32:06 2025 +0000 |
| tree | 70accb9e51507c33e5ba25616c2118fbba6cabbe | |
| parent | 3729f65a78c43efeec39bab2cfe216d908ca8051 [diff] |
pvmfw: Only configure PCI if instance.img required As some guests now implement rollback protection using other means than instance.img (virtio-blk over virtio-pci), only conditionally initialize the PCI bus (including issuing the corresponding MMIO_GUARD HVCs) when actually needed. Note that the VirtIO configuration (and corresponding MEM_SHARE HVCs) was already limited to cases accessing the instance.img. Bug: 377276983 Test: m pvmfw_bin Change-Id: I600870dbbae9e8722a6258e066ea714dd29ecf44
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: