pageout_bomb: new command to MADV_PAGEOUT all processes in the guest

This is intended to be an alternative to inflating the balloon. The main
side effect of inflating the balloon to max is that it drops caches in
the kernel and forces userspace memory into swap. The theory here is
that it would be better to do those things directly, with the advantage
that there is less risk of causing OOMs (because MemAvailable doesn't go
down) and then let VIRTIO_BALLOON_F_PAGE_REPORTING release the pages to
the guest proactively.

Using `setprop pageout_bomb.go 1` (invokes pageout_bomb via init rc
files) gives worse results than shelling into the VM and invoking
`/system/bin/payout_bomb` directly. It may be because `init` touches a
fair amount of pages as part of reaping the process.

Bug: 418304368
Test: launch microdroid VM, connect, `setprop pageout_bomb.go 1`, see memory usage go down
Flag: EXEMPT ...
Change-Id: Iab7a1d51f6a01e3b58772251c405e62a96280887
4 files changed
tree: 366bfab5ec794acbabf47d90890e56c67b3ca0a5
  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: