always add swiotlb size to memory size for protected VMs

This should be a noop when paired with https://crrev.com/c/5637774.
Before that CL, there was an inconsistency in crosvm that essentially
added extra physical memory equivalent to the swiotlb size for
hypervisors requireing static swiotlb allocation (i.e. everything but
pKVM). https://crrev.com/c/5637774 essentially reduces the RAM size by
`swiotlb_size_mib` and then this CL adds `swiotlb_size_mib` back.

Bug: 346770542
Test: launched microdroid and checked --mem argument
Change-Id: I7fa13962abfe7953ceb027cfd8817831a6dec5aa
2 files changed
tree: c88fbca4e4886ecb8e82b136b367f52494ee1bc4
  1. apex/
  2. apkdmverity/
  3. authfs/
  4. compos/
  5. demo/
  6. demo_native/
  7. docs/
  8. encryptedstore/
  9. ferrochrome_app/
  10. flags/
  11. java/
  12. launcher/
  13. libs/
  14. microdroid/
  15. microdroid_manager/
  16. pvmfw/
  17. rialto/
  18. service_vm/
  19. tests/
  20. virtualizationmanager/
  21. virtualizationservice/
  22. vm/
  23. vm_payload/
  24. vmbase/
  25. vmclient/
  26. vmlauncher_app/
  27. zipfuse/
  28. .clang-format
  29. .gitignore
  30. Android.bp
  31. avf_flags.aconfig
  32. OWNERS
  33. PREUPLOAD.cfg
  34. README.md
  35. rustfmt.toml
  36. 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: