Restrict RELEASE_AVF_ENABLE_EARLY_VM flag to only trunk_staging

We should make sure that we don't accidentally enable
RELEASE_AVF_ENABLE_EARLY_VM in -next release configuration before
b/357025924 is fixed.

Since it seems we can't query the value of TARGET_RELEASE, we use
RELEASE_AIDL_USE_UNFROZEN as a proxy (it is set to true in non-next
release configurations)

Bug: 357025924
Test: set RELEASE_AVF_ENABLE_EARLY_VM to true in ap2a release
Test: check that build fails
Change-Id: I83eb1f17c27f63923e0c4102328e71f860af726d
1 file changed
tree: b8f772e1adda29e4b5fbae7b822f3ec9822836aa
  1. android/
  2. build/
  3. docs/
  4. guest/
  5. libs/
  6. microfuchsia/
  7. tests/
  8. .clang-format
  9. .gitignore
  10. Android.bp
  11. dice_for_avf_guest.cddl
  12. OWNERS
  13. PREUPLOAD.cfg
  14. README.md
  15. rustfmt.toml
  16. TEST_MAPPING
README.md

Android Virtualization Framework (AVF)

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: