----- Original Message ----- > Describe dom0 support in the config menu and supply help text for it. > > v2 adds 'if EXPERT' to keep it out of the "standard" menu. > > Signed-off-by: Andrew Jones <drjones@xxxxxxxxxx> > --- > arch/x86/xen/Kconfig | 7 ++++++- > 1 files changed, 6 insertions(+), 1 deletions(-) > > diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig > index 26c731a..31ec975 100644 > --- a/arch/x86/xen/Kconfig > +++ b/arch/x86/xen/Kconfig > @@ -14,9 +14,14 @@ config XEN > Xen hypervisor. > > config XEN_DOM0 > - def_bool y > + bool "Xen Initial Domain (Dom0) support" if EXPERT > + default y > depends on XEN && PCI_XEN && SWIOTLB_XEN > depends on X86_LOCAL_APIC && X86_IO_APIC && ACPI && PCI > + help > + This allows the kernel to be used for the initial Xen domain, > + Domain0. This is a privileged guest that supplies backends > + and is used to manage the other Xen domains. > > # Dummy symbol since people have come to rely on the > PRIVILEGED_GUEST > # name in tools. > -- > 1.7.7.5 There's currently an issue using EXPERT. It doesn't make this patch wrong, but any users that would want to turn EXPERT on, in order to turn DOM0 off, would find that their configs have gotten twisted in other ways as well. I've posted a patch for EXPERT, and if it gets merged, then I really can't see any good arguments against this patch. Drew _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
