| commit | 1ba9b4ade8becd5f75ff54c8249f11ea958afddc | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue May 28 22:21:57 2024 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue May 28 22:21:57 2024 +0900 |
| tree | 2b33e986f322fa82f22e98ad48c9a25e456ba384 | |
| parent | 569d56e364426458106260488192feb22e7e8648 [diff] |
Serial devices follows the legacy order crosvm uses the same legacy order (3f8, 2f8, 3e8, 2e8) across x86 and arm64. crosvm once tried to change that for non-x86 architecture (because it doesn't have to), but that didn't land because there were existing use case where the legacy order is expected. This change makes sure that the serial device order is not changed by the rewrite of the device tree by pvmfw. Bug: 330659544 Test: run microdroid in pvm and check the kernel log Change-Id: I3cfecc882148d0d1edd1a699123a0d26cee9ce95
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: