| commit | 80ef9faec11699ef14804fd0a0d71ba72a776a29 | [log] [tgz] |
|---|---|---|
| author | Jaewan Kim <jaewan@google.com> | Sun Feb 25 16:08:14 2024 +0000 |
| committer | Jaewan Kim <jaewan@google.com> | Sat Mar 02 00:06:00 2024 +0900 |
| tree | cb8bdc298a0dd8cb03accc22d2ac52fc6098e41a | |
| parent | 371f6c8138c7fb8f6e436281f637b66529a30a87 [diff] |
pvmfw: Allow non-assignable device nodes to be labeled Assignable devices list is provided by the XML, so validating whether the labeled nodes is valid device node is too much check and only makes writing DT hard. This CL relax the condition by not returning error for labeled nodes that aren't backed by physical device nodes. Bug: 323453334 Test: Manually with markdown preview \ atest libpvmfw.device_assignment.test Change-Id: I98e0173f9536d52c1fd8eb40075c67c2361ce52c
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: