| commit | 2174d411d3735e03e00bfa4650db4795cc595545 | [log] [tgz] |
|---|---|---|
| author | Shikha Panwar <shikhapanwar@google.com> | Fri Sep 22 14:18:46 2023 +0000 |
| committer | Shikha Panwar <shikhapanwar@google.com> | Mon Sep 25 12:35:22 2023 +0000 |
| tree | b4350a33804c4dff618b98ce231d06f0624f1160 | |
| parent | f7c0f9401274deb81657e5906fe958af94e316d9 [diff] |
Skip changingDebuggability related tests on Non-pVM These are boot tests (more precisely, they test that VM does not boot) when debuggability is changed. Debuggability changes the initrd which is verified by pvmfw. They dont make much sense in cases of non-protected VM where pvmfw is not in boot seq. Note: the test still pass for non-protected VM on devices without debug policy, the reason for that is an extra apex 'adbd' is included in the VM, which results in MicrodroidData 'mismatch' result in boot failure. But that is not the point of the test. Bug: 301014052 Test: atest #changingNonDebuggableVmDebuggableInvalidatesVmIdentity & check that it is indeed skipped Change-Id: Ic2818a8f513c778ad1f5217d3641398c8df1719d
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:
How-Tos: