argo: Introduce the Kconfig option to govern inclusion of Argo

Defines CONFIG_ARGO when enabled. Default: disabled.

When the Kconfig option is enabled, the Argo hypercall implementation
will be included, allowing use of the hypervisor-mediated interdomain
communication mechanism.

Argo is implemented for x86 and ARM hardware platforms.

Availability of the option depends on EXPERT and Argo is currently an
experimental feature.

Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Release-acked-by: Juergen Gross <jgross@suse.com>

diff --git a/xen/common/Kconfig b/xen/common/Kconfig
index a79cd404416b7d621863c825c23918d69fd525b5..04384628bb2673a6d485deac20ef66826530093d 100644 (file)
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -202,6 +202,25 @@ config LATE_HWDOM
 
          If unsure, say N.
 
+config ARGO
+       bool "Argo: hypervisor-mediated interdomain communication" if EXPERT = "y"
+       ---help---
+         Enables a hypercall for domains to ask the hypervisor to perform
+         data transfer of messages between domains.
+
+         This allows communication channels to be established that do not
+         require any shared memory between domains; the hypervisor is the
+         entity that each domain interacts with. The hypervisor is able to
+         enforce Mandatory Access Control policy over the communication.
+
+         If XSM_FLASK is enabled, XSM policy can govern which domains may
+         communicate via the Argo system.
+
+         This feature does nothing if the "argo" boot parameter is not present.
+         Argo is disabled at runtime by default.
+
+         If unsure, say N.
+
 menu "Schedulers"
        visible if EXPERT = "y"