| commit | 631717e1b4a9e8d8d8d5ff6a35f4add559df80c8 | [log] [tgz] |
|---|---|---|
| author | Nikita Ioffe <ioffe@google.com> | Tue Sep 05 13:38:07 2023 +0100 |
| committer | Nikita Ioffe <ioffe@google.com> | Tue Sep 05 16:30:18 2023 +0100 |
| tree | 13fd39baa84a8b4326f70ae93a0524f81fe27b4c | |
| parent | f7c742ac8abbe23d308e68a082c02d675f72b0ea [diff] |
Flag guard the code related to the vendor modules feature The feature is guarded by the RELEASE_AVF_ENABLE_VENDOR_MODULES flag. On the virtmgr side the flag-guard check is done in the create_vm_internal function. On the vm binary side the related flags (--vendor, --kernel) are only enabled if the RELEASE_AVF_ENABLE_VENDOR_MODULES flag is enabled. Additionally the vendor modules related tests in MicrodroidTests now run conditionally depending on the result of the `isFeatureEnabled(FEATURE_VENDOR_MODULES)` call. Bug: 298007909 Test: atest MicrodroidTests Change-Id: I1467194c802720601a10d0a760a8f1d7ce134037
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:
How-Tos: