commit | 22e5d0a0b7e5109245cb15b4dbf1c47f71804d81 | [log] [tgz] |
---|---|---|
author | Nikita Ioffe <ioffe@google.com> | Mon Feb 17 16:36:52 2025 +0000 |
committer | Nikita Ioffe <ioffe@google.com> | Mon Mar 03 17:48:45 2025 +0000 |
tree | c12d889da5a2de79d2d847a5b8dce631c0bdf45a | |
parent | 87282311827840dc708991a07dde5e444df0b352 [diff] |
virtmgr: also support non-vendor tee services We are going to reuse the teeServices field of the VirtualMachineRawConfig to also handle cases of generic "system" tee services. First such case (guest-ffa-proxy) will be added in the follow-up patch. This patch simply splits teeServices into "vendor" (name has vendor. prefix) and "system" (the rest). The handling of the "vendor" tee services will be partially delegated to the IVmCapabilitiesService HAL in one of the follow-up patches, while handling of the "system" tee services will be entirely done between virtmgr & crosvm. Bug: 391774181 Bug: 360102915 Test: presubmit Change-Id: I9ef85475204ed53a56dbf2c25661a7c0b0da3cb0
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: