| commit | 82aaf03f6f66fbb3cfe56882aeedb5e9d036c58a | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Wed Oct 30 21:00:38 2024 +0000 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Mon Nov 04 15:34:12 2024 +0000 |
| tree | c2674865f23cd70f795a7a5d06d7f10e470dedd3 | |
| parent | 4e9d2f6815a9317ca4a81e92bc8e01f99ee0b19c [diff] |
vmbase: Add CPU-specific submodules to crate::arch Add a crate that will be used to provide CPU architecture-agnostic functionality to which we will eventually move all the AArch64-specific code currently present in vmbase, pvmfw, and Rialto. Submodule names follow the rustc target_arch config. Test: m pvmfw_bin Bug: 377276983 Change-Id: I48eae23b6dfd5a42e4b523d34d498687df0dbb9e
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: