On 19/10/18 15:28, Wei Liu wrote: > Change "guest" to "domain" where appropriate because "guest" doesn't > include Domain 0. > > Signed-off-by: Wei Liu <wei.l...@citrix.com> > --- > v2: new > --- > xen/arch/x86/Kconfig | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig > index c7e97e2..b4bd83e 100644 > --- a/xen/arch/x86/Kconfig > +++ b/xen/arch/x86/Kconfig > @@ -70,12 +70,12 @@ config HVM > def_bool !PV_SHIM_EXCLUSIVE > prompt "HVM support" > ---help--- > - Interfaces to support HVM guests which require hardware > + Interfaces to support HVM domains 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. > + doesn't distinguish HVM or PVH. PVH is only a concept for > + end users.
Matching the PV suggestion, how about: Interfaces to support HVM domains. HVM domains requires hardware virtualisation extensions (e.g. Intel VT-x, AMD SVM), but can boot guests which have no specific Xen knowledge. ? ~Andrew > > - 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. > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
