[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH v2 01/18] argo: Introduce the Kconfig option to govern inclusion of Argo

Signed-off-by: Christopher Clark <christopher.clark6@xxxxxxxxxxxxxx>
Changes since v1:

Change the default to disabled.
Make the prompt depend on EXPERT.
Fix tab-based indentation.

 xen/common/Kconfig | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/xen/common/Kconfig b/xen/common/Kconfig
index 68132a3..b5a1b29 100644
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -200,6 +200,26 @@ config LATE_HWDOM
          If unsure, say N.
+config ARGO
+       def_bool n
+       prompt "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"

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.