FF-A: map whole system memory to Hypervisor VM
The "Hypervisor VM" is an abstract representation of the NWd
(Hypervisor or OS kernel if no EL2 present) from the perspective
of the SPMC. vCPUs for such VM (or SP) are never scheduled.
Therefore the corresponding page tables are never rooted into
any physical PE. For any FF-A call from NWd to SWd, the SPMC
is resumed from ffa_handler_loop. At this stage the "current"
vCPU passed to the ffa_handler is one of the "Hypervisor VM"
of FF-A id 0. This serves different purposes (non-exhaustively):
tracking NWd to SWd mem share operations, mapping of Hypervisor
RX/TX buffers, partition info get forwarded from NWd to SWd.
There is the same concept of "TEE VM" from the perspective of
the Hypervisor in NWd. The "Hypervisor VM" is the similar concept
extended to the SWd.
Change-Id: I2d2e77c41825ef1a59a320e75d6b647c43966135
Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
diff --git a/src/init.c b/src/init.c
index 03fc2fd..a5b48ab 100644
--- a/src/init.c
+++ b/src/init.c
@@ -11,7 +11,7 @@
#include <stdalign.h>
#include <stddef.h>
-#include "hf/arch/tee.h"
+#include "hf/arch/other_world.h"
#include "hf/api.h"
#include "hf/boot_flow.h"
@@ -169,7 +169,7 @@
if (manifest.ffa_tee_enabled) {
/* Set up message buffers for TEE dispatcher. */
- arch_tee_init();
+ arch_other_world_init();
}
dlog_info("Hafnium initialisation completed\n");