From: Andrew Jones <drjones@redhat.com>
To: xen-devel@lists.xensource.com
Cc: jeremy@goop.org, virtualization@lists.linux-foundation.org,
konrad.wilk@oracle.com
Subject: [PATCH 3/4] xen kconfig: add dom0 support help text
Date: Fri, 6 Jan 2012 10:43:10 +0100 [thread overview]
Message-ID: <1325842991-4404-4-git-send-email-drjones@redhat.com> (raw)
In-Reply-To: <1325842991-4404-1-git-send-email-drjones@redhat.com>
Describe dom0 support in the config menu and supply help text for it.
Signed-off-by: Andrew Jones <drjones@redhat.com>
---
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..88862d5 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"
+ 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
next prev parent reply other threads:[~2012-01-06 9:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:43 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06 9:43 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones
2012-01-06 9:43 ` [PATCH 2/4] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps Andrew Jones
2012-01-06 15:46 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-06 15:58 ` Andrew Jones
2012-01-09 7:59 ` Dmitry Torokhov
2012-01-09 10:43 ` [Xen-devel] " Andrew Jones
2012-01-09 17:51 ` [PATCH 2/4 v2] " Andrew Jones
2012-01-11 16:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-11 16:29 ` Andrew Jones
2012-03-15 17:23 ` Konrad Rzeszutek Wilk
2012-03-16 6:24 ` Dmitry Torokhov
2012-03-16 14:48 ` Konrad Rzeszutek Wilk
2012-01-23 18:35 ` [PATCH 2/4] " Konrad Rzeszutek Wilk
2012-01-06 9:43 ` Andrew Jones [this message]
2012-01-09 18:07 ` [PATCH 3/4 v2] xen kconfig: add dom0 support help text Andrew Jones
2012-01-11 15:45 ` [Xen-devel] " Andrew Jones
2012-01-23 18:42 ` [PATCH 3/4] " Konrad Rzeszutek Wilk
2012-01-06 9:43 ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
2012-01-23 18:34 ` Konrad Rzeszutek Wilk
2012-01-24 8:30 ` Igor Mammedov
2012-01-24 17:38 ` [Xen-devel] " Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2012-01-06 12:35 [Xen-devel] [PATCH 3/4] xen kconfig: add dom0 support help text Stefano Stabellini
2012-01-06 12:43 ` Andrew Jones
2012-01-06 11:21 [Xen-devel] " Stefano Stabellini
2012-01-06 12:24 ` Andrew Jones
2012-01-06 9:55 [Xen-devel] " Ian Campbell
2012-01-06 10:45 ` Andrew Jones
2012-01-06 8:57 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06 8:57 ` [PATCH 3/4] xen kconfig: add dom0 support help text Andrew Jones
2012-01-06 9:20 ` Ian Campbell
2012-01-06 9:26 ` Andrew Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1325842991-4404-4-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).