| commit | 50b490abe5a24f7498c57aa7e08cdb676bfa46f8 | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Tue Jun 18 20:28:29 2024 +0100 |
| committer | Pierre-Clément Tosi <ptosi@google.com> | Mon Jul 08 14:27:04 2024 +0100 |
| tree | 73d2f71ac38c912974e383f8899d30d0bfc2cfa4 | |
| parent | 0bd9808f28be25ffa9095cb5fb8e48a677a0d768 [diff] |
vmbase: Replace emergency_write_str with eprintln! Similar to vmbase_example and pvmfw, use the macro in Rialto, instead of the function directly. Update the README to only recommend eprintln!() as the comment about emergency_write_str() not accessing the stack is not guaranteed (and relies on an implementation-defined behavior of the compiler), which is less likely to be relevant since aosp/2550864 as synchronous exception handlers now have a dedicated stack. Test: m pvmfw librialto libvmbase_example Change-Id: Ia2c90b0c2896016fa93a0f2cd326ae72844a9c84
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: