MicrodroidConfig: Unify API across flag configs

Flags should control the behavior of the code but using different APIs
with different flag configurations makes the code harder to reason about
when making a modification (in particular because flags configurations
aren't all tested at the same rate and a build breakage might be hard to
detect) so unfiy the different flag-defined "variants" of a same method
under a same signature.

In this process, improve the existing signatures:

 - prefer "-> Option<&T>" over "-> &Option<T>" as it's easier to
   generate, manipulate, and reason about

 - prefer "-> &[T]" over "-> &Vec<T>" as it is more flexible, hiding an
   implementation detail about the internal representation, and is
   typically the recommended type to use in an API

Note: No functional change intended.

Test: banchan com.android.virt aosp_arm64 && m apps_only dist
Change-Id: I240d0bb0f1d6c630c89f2939261eed021912d01d
1 file changed
tree: 154ca50783f90b181536d51b4a2a9b0da9a2d852
  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: