| commit | 6dcf308e99fe9a560f1230ee826042da29661b04 | [log] [tgz] |
|---|---|---|
| author | Jaewan Kim <jaewan@google.com> | Fri Jan 10 16:30:27 2025 +0900 |
| committer | Jaewan Kim <jaewan@google.com> | Wed Jan 15 15:39:10 2025 +0900 |
| tree | ed682dc6ae53648a07c232ace7159d448e406867 | |
| parent | 6808678571f35b4ce54c715c0bd05e25a4b34b3b [diff] |
libvmclient: Take VmCallback in VmInstance::start()
Taking VmCallback from VmInstance::new() has following issues:
- Hard to manage VmInstance and VmCallback together,
becaues VmInstance is available after Callback is instantiated.
- VmCallback is only called after being started.
Bug: 381195543
Test: T/H
Change-Id: I013dce6371156ed298a612582c392a54768c00d6
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: