commit 5ad1e8c18fcb86175f483d664a19f0604b28ec67
author Pierre-Clément Tosi <ptosi@google.com> Thu Jun 29 10:36:48 2023 +0000
committer Pierre-Clément Tosi <ptosi@google.com> Fri Jul 07 10:40:59 2023 +0000
tree c213ef45d8d93e4fa1e13fb04e495f45ed030bf9
parent 8937cb8cb1e8f90becd64e2d2086fe4a608d3cb2

hyp: Introduce HypervisorCap::MMIO_GUARD

Similarly to DYNAMIC_MEM_SHARE, introduce a capability that client code
can check before calling MMIO_GUARD functions. This will remove the need
to implement stubs in the backends due to client code unconditionally
calling the functions.

Note that KvmHypervisor currently covers both pKVM and non-protected KVM
and will therefore have HypervisorCap::MMIO_GUARD, for now. As the only
client code that makes use of MMIO_GUARD and is intended to run on both
pKVM and regular KVM, Rialto, already deals with the distinction, this
patch doesn't deal with differentiating between the two modes, which is
done in a following patch.

No functional change intended.

Test: atest DebugPolicyHostTests#testNoAdbInDebugPolicy_withDebugLevelNone_boots
Test: atest rialto_test vmbase_example.integration_test
Change-Id: If45d31e65b2407deaf4df16cd4d354ccd6bf4506