From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v3 7/7] x86: update help string for CONFIG_HVM
Date: Fri, 2 Nov 2018 15:55:45 +0000 [thread overview]
Message-ID: <4d892f7f59b5fef0dbb62ac5c96d2549faa3ba03.1541174103.git-series.wei.liu2@citrix.com> (raw)
In-Reply-To: <cover.39d7afa1de7ac30224aa95827f791db8d5650fde.1541174103.git-series.wei.liu2@citrix.com>
Update text. Change "guest" to "domain" where appropriate because
"guest" doesn't include Domain 0.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
v3: update text
v2: new
---
xen/arch/x86/Kconfig | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
index 37af728..5c2d107 100644
--- a/xen/arch/x86/Kconfig
+++ b/xen/arch/x86/Kconfig
@@ -70,12 +70,11 @@ config HVM
def_bool !PV_SHIM_EXCLUSIVE
prompt "HVM support"
---help---
- Interfaces to support HVM guests which require hardware
- support like Intel's VT-x or AMD's SVM. Note the hypervisor
- doesn't distinguish HVM or PVH guest types. PVH guest type
- is only a concept for end users.
+ Interfaces to support HVM domains. HVM domains require hardware
+ virtualisation extensions (e.g. Intel VT-x, AMD SVM), but can boot
+ guests which have no specific Xen knowledge.
- This option is needed if you want to run HVM or PVH guests.
+ This option is needed if you want to run HVM or PVH domains.
If unsure, say Y.
--
git-series 0.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-02 15:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 15:55 [PATCH v3 0/7] Make CONFIG_PV work on x86 Wei Liu
2018-11-02 15:55 ` [PATCH v3 1/7] x86: make traps.c build with !CONFIG_PV Wei Liu
2018-11-05 14:07 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 2/7] x86/domctl: rework XEN_DOMCTL_{set, get}_address_size Wei Liu
2018-11-05 14:08 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 3/7] x86: make PV hypercall entry points work with !CONFIG_PV Wei Liu
2018-11-05 14:13 ` Andrew Cooper
2018-11-05 15:04 ` Jan Beulich
2018-11-05 15:48 ` Wei Liu
2018-11-05 15:49 ` Andrew Cooper
2018-11-05 15:51 ` Wei Liu
2018-11-05 16:11 ` Jan Beulich
2018-11-08 15:33 ` Wei Liu
2018-11-08 15:36 ` Andrew Cooper
2018-11-08 15:49 ` Jan Beulich
2018-11-08 16:09 ` Wei Liu
2018-11-08 16:22 ` Jan Beulich
2018-11-08 16:42 ` Wei Liu
2018-11-08 15:39 ` Jan Beulich
2018-11-08 15:49 ` Wei Liu
2018-11-02 15:55 ` [PATCH v3 4/7] x86: rearrange x86_64/entry.S Wei Liu
2018-11-05 14:20 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 5/7] x86: make entry point code build when !CONFIG_PV Wei Liu
2018-11-05 14:33 ` Andrew Cooper
2018-11-05 17:08 ` Wei Liu
2018-11-05 17:10 ` Andrew Cooper
2018-11-02 15:55 ` [PATCH v3 6/7] x86: expose CONFIG_PV Wei Liu
2018-11-02 15:55 ` Wei Liu [this message]
2018-11-05 15:20 ` [PATCH v3 7/7] x86: update help string for CONFIG_HVM Jan Beulich
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=4d892f7f59b5fef0dbb62ac5c96d2549faa3ba03.1541174103.git-series.wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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).