pvmfw: Do iommus validation for pkvm-pviommu only

There are VMs not using pkvm-pviommu. For example, some Qualcomm
VMs. In that case, there will be devices using iommus. So the device
node will be having iommus=< >, defined. But it's physical device under
/host node in VM dtbo will not have iommus property. This patch decides
to validate only if the trustable physical node under /host has any iommu.
Otherwise ignore iommus from crosvm and skip validation.

Test: m libpvmfw.device_assignment.test pvmfw
Bug: 380074580
Bug: 385802423
Change-Id: I9ad5d1da9561ec0ae19b0cc6d69d02de2ddffd1f
Signed-off-by: Sreenad Menon <quic_sreemeno@quicinc.com>
1 file changed
tree: 7af69efcf16da2b62502902665c678275b6e8763
  1. android/
  2. build/
  3. docs/
  4. guest/
  5. libs/
  6. microfuchsia/
  7. tests/
  8. .clang-format
  9. .gitignore
  10. Android.bp
  11. dice_for_avf_guest.cddl
  12. OWNERS
  13. PREUPLOAD.cfg
  14. README.md
  15. rustfmt.toml
  16. TEST_MAPPING
README.md

Android Virtualization Framework (AVF)

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: