| commit | d42aa2cf2c0103a11acf15be34c843d8a0ec6870 | [log] [tgz] |
|---|---|---|
| author | Jakob Vukalovic <jakobvukalovic@google.com> | Thu Nov 09 16:04:00 2023 +0000 |
| committer | Jakob Vukalovic <jakobvukalovic@google.com> | Mon Dec 18 17:36:38 2023 +0000 |
| tree | 9476de3573ac16ed121563911ccdef1c2db747df | |
| parent | 226e3ea3ef8b26539299dddd7aaff0428b1a0447 [diff] |
virtualizationservice: Unbind devices on VM exit When configured to assign VFIO devices to a VM, virtualizationmanager will bind them to the VFIO driver before starting the VM. This change rebinds the default driver after VM exit, so the devices can be used by the host again. Test: Assign a device to VM, then check `<device_sysfs>/driver` post exit Bug: 278008519 Change-Id: I48eee0b0dc1bba40a1c0c543d74f47ec4fee6d78
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: