On Mon, Feb 25, 2013 at 12:39:27PM +0000, Stefano Stabellini wrote:

On Sun, 24 Feb 2013, Greg Kroah-Hartman wrote:

quoted

On Sun, Feb 24, 2013 at 05:51:44PM +0800, Dongsheng Song wrote:

quoted

On Sun, Feb 24, 2013 at 1:03 AM, Kees Cook [off-list ref] wrote:

quoted

On Sat, Feb 23, 2013 at 3:59 AM, Dongsheng Song
[off-list ref] wrote:

quoted

On Sat, Feb 23, 2013 at 3:29 PM, Kees Cook [off-list ref] wrote:

quoted

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 <redacted>
Cc: Stefano Stabellini <redacted>
Cc: Mukesh Rathor <redacted>
Cc: Konrad Rzeszutek Wilk <redacted>
---
 arch/x86/xen/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
index 93ff4e1..8cada4c 100644
--- a/arch/x86/xen/Kconfig
+++ b/arch/x86/xen/Kconfig

@@ -53,7 +53,7 @@ config XEN_DEBUG_FS

 config XEN_X86_PVH
        bool "Support for running as a PVH guest (EXPERIMENTAL)"

Why not remove this 'EXPERIMENTAL' too ?

It was unclear to me if the feature was actually considered unstable.
I can resend with the text removed from the title too, if that's the
correct action here?

-Kees

If such a feature was considered unstable, it should depends on EXPERIMENTAL.

CONFIG_EXPERIMENTAL is going away.

quoted

We should not surprised users.

You should not have unstable options in the kernel in the first place,
sorry.

Just to clarify - this 'unstable' part is that the hypercall interface has
not been nailed down. As such the patchseries ('PVH') is not going in
Linus's tree until that is nailed down. However, the 'PVH' is going in
in 3.10 merge window (barring again delays).

Initially it was scheduled to be in v3.8, hence the reason it has
been lingering in #linux-next.

 
With the premise that the removal of CONFIG_EXPERIMENTAL is not an issue
for me personally or my work, I am going to give you my 2 cents on the
matter, but feel free to ignore them :)

While I understand that CONFIG_EXPERIMENTAL has been abused, I feel that
rejecting everything that is not fully stable and with external
interfaces set in stones, might hinder the development of new features.

After all, given how fast the kernel is moving nowadays, maintaining a
project out-of-tree until is completely ready for production can be
very expensive. Merging the project earlier and completing the
development upstream can bring better results. But in these cases one
wouldn't want to "market" the feature as stable yet, because it just
isn't. If CONFIG_EXPERIMENTAL is going away, is there anything in the
kernel that can be used to tag a feature as "I wouldn't use it in
production if I were you"? Maybe just a comment in the kconfig
description?