Kees Cook
2013-Feb-28 21:56 UTC
[PATCH v2] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a while now and is almost always enabled by default. As agreed during the Linux kernel summit, remove it from any "depends on" lines in Kconfigs. Signed-off-by: Kees Cook <keescook at chromium.org> Cc: Stefano Stabellini <stefano.stabellini at eu.citrix.com> Cc: Mukesh Rathor <mukesh.rathor at oracle.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> --- v2: - drop EXPERIMENTAL from bool and help text too. --- arch/x86/xen/Kconfig | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index 93ff4e1..6c5802f 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -52,12 +52,10 @@ config XEN_DEBUG_FS Enabling this option may incur a significant performance overhead. config XEN_X86_PVH - bool "Support for running as a PVH guest (EXPERIMENTAL)" - depends on X86_64 && XEN && EXPERIMENTAL + bool "Support for running as a PVH guest" + depends on X86_64 && XEN default n help This option enables support for running as a PVH guest (PV guest using hardware extensions) under a suitably capable hypervisor. - This option is EXPERIMENTAL because the hypervisor interfaces - which it uses is not yet considered stable therefore backwards and - forwards compatibility is not yet guaranteed. If unsure, say N. + If unsure, say N. -- 1.7.9.5 -- Kees Cook Chrome OS Security
Stefano Stabellini
2013-Feb-28 22:53 UTC
[PATCH v2] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
On Thu, 28 Feb 2013, Kees Cook wrote:> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a > while now and is almost always enabled by default. As agreed during the > Linux kernel summit, remove it from any "depends on" lines in Kconfigs. > > Signed-off-by: Kees Cook <keescook at chromium.org> > Cc: Stefano Stabellini <stefano.stabellini at eu.citrix.com> > Cc: Mukesh Rathor <mukesh.rathor at oracle.com> > Cc: Konrad Rzeszutek Wilk <konrad.wilk at oracle.com> > --- > > v2: > - drop EXPERIMENTAL from bool and help text too. > > --- > arch/x86/xen/Kconfig | 8 +++----- > 1 file changed, 3 insertions(+), 5 deletions(-) > > diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig > index 93ff4e1..6c5802f 100644 > --- a/arch/x86/xen/Kconfig > +++ b/arch/x86/xen/Kconfig > @@ -52,12 +52,10 @@ config XEN_DEBUG_FS > Enabling this option may incur a significant performance overhead. > > config XEN_X86_PVH > - bool "Support for running as a PVH guest (EXPERIMENTAL)" > - depends on X86_64 && XEN && EXPERIMENTAL > + bool "Support for running as a PVH guest" > + depends on X86_64 && XEN > default n > help > This option enables support for running as a PVH guest (PV guest > using hardware extensions) under a suitably capable hypervisor. > - This option is EXPERIMENTAL because the hypervisor interfaces > - which it uses is not yet considered stable therefore backwards and > - forwards compatibility is not yet guaranteed. If unsure, say N. > + If unsure, say N.Please do not change the text this way. The fact that CONFIG_EXPERIMENTAL is going away it doesn't change the fact that this feature is experimental. Maybe you want to replace EXPERIMENTAL with experimental, or if experimental has become as taboo word, I am sure you can find a suitable synonym.
Seemingly Similar Threads
- [PATCH v2] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
- [PATCH] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
- [PATCH] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
- [PATCH RFC v2] pvh: clearly specify used parameters in vcpu_guest_context
- [PATCH]: PVH: specify xen features strings cleany for PVH