pvmfw: Refactor pKVM HVCs
Instead of assuming that pKVM is the only hypervisor that pvmfw will
run on, introduce a new module to host the back-end interfaces and
clarify that the HVCs we currently have are pKVM-specific.
Note: no functional change intended.
Bug: 271493784
Test: TH
Change-Id: Ie96556afbdff585a87319046e3b0dc9bf00b87f9
diff --git a/pvmfw/src/memory.rs b/pvmfw/src/memory.rs
index 86fcd00..17dd36b 100644
--- a/pvmfw/src/memory.rs
+++ b/pvmfw/src/memory.rs
@@ -17,7 +17,7 @@
#![deny(unsafe_op_in_unsafe_fn)]
use crate::helpers::{self, align_down, align_up, page_4kb_of, SIZE_4KB};
-use crate::hvc::{hyp_meminfo, mem_share, mem_unshare};
+use crate::hypervisor::{hyp_meminfo, mem_share, mem_unshare};
use crate::mmio_guard;
use crate::mmu;
use crate::smccc;