Documenting Hafnium expectations of scheduler VM.
Bug: 141469322
Change-Id: Icadfd63a4e55a51108446534c02d06c7ae7a5e1b
diff --git a/docs/VmInterface.md b/docs/VmInterface.md
index e943ff8..1a8fd6f 100644
--- a/docs/VmInterface.md
+++ b/docs/VmInterface.md
@@ -5,9 +5,10 @@
more direct access to some hardware, and 'secondary VMs' which exist mostly to
provide services to the primary VM, and have a more paravirtualised interface.
The intention is that the primary VM can run a mostly unmodified operating
-system (such as Linux) with the addition of a Hafnium driver, while secondary
-VMs will run more specialised trusted OSes or bare-metal code which is designed
-with Hafnium in mind.
+system (such as Linux) with the addition of a Hafnium driver which
+[fulfils certain expectations](SchedulerExpectations.md), while secondary VMs
+will run more specialised trusted OSes or bare-metal code which is designed with
+Hafnium in mind.
The interface documented here is what is planned for the first release of
Hafnium, not necessarily what is currently implemented.