From: Denis Mukhin <dmukhin@ford.com> 

Remove XEN_CONFIG_EXPERT explanation and also correct information in
the entire "Xen Hypervisor" section.

Amends: 37339ba9ef46 ("automation: Remove XEN_CONFIG_EXPERT leftovers")
Suggested-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Denis Mukhin <dmukhin@ford.com>
---
Changes since v2:
- Applied suggested edits to the entire section suggested by Stefano
- Link to v2: https://lore.kernel.org/xen-devel/20260116030842.415583-2-dmukhin@ford.com/
---
 INSTALL | 19 ++++++-------------
 1 file changed, 6 insertions(+), 13 deletions(-)

diff --git a/INSTALL b/INSTALL
index c2e756bf4b2b..670cbc2fa3b8 100644
--- a/INSTALL
+++ b/INSTALL
@@ -25,19 +25,12 @@ Xen Hypervisor
 Xen itself is configured via a `kconfig' system borrowed from Linux.
 See https://www.kernel.org/doc/html/v5.4/kbuild/.
 
-Note that unlike with Linux, and contrary to that document, you cannot
-look at Kconfig files, or the default or generated config files etc.,
-to find available configuration options.  This is because it is only
-supported (and security supported) by the Xen Project, to change a
-small subset of the options.  Attempts to change other options will be
-silently overridden.  The only way to find which configuration options
-are available is to run `make menuconfig' or the like.
-
-You can counter-override this behaviour by setting XEN_CONFIG_EXPERT=y
-in your environment.  However, doing this is not supported and the
-resulting configurations do not receive security support.  If you set
-this variable there is nothing stopping you setting dangerously
-experimental combinations of features - not even any warnings.
+Only a subset of options is supported or security-supported by Xen
+Project. You can explore all available options, including unsupported
+ones and those recommended only for expert users, by using `make
+menuconfig` and enabling `CONFIG_UNSUPPORTED` and/or `CONFIG_EXPERT`.
+However, enabling these options is not supported, and configurations
+resulting from them do not receive security support.
 
 Options recognized by configure
 ===============================
-- 
2.52.0

On 20.01.2026 08:16, dmukhin@xen.org wrote:
> From: Denis Mukhin <dmukhin@ford.com> 
> 
> Remove XEN_CONFIG_EXPERT explanation and also correct information in
> the entire "Xen Hypervisor" section.
> 
> Amends: 37339ba9ef46 ("automation: Remove XEN_CONFIG_EXPERT leftovers")
> Suggested-by: Stefano Stabellini <sstabellini@kernel.org>
> Signed-off-by: Denis Mukhin <dmukhin@ford.com>

Acked-by: Jan Beulich <jbeulich@suse.com>
preferably with ...

> --- a/INSTALL
> +++ b/INSTALL
> @@ -25,19 +25,12 @@ Xen Hypervisor
>  Xen itself is configured via a `kconfig' system borrowed from Linux.
>  See https://www.kernel.org/doc/html/v5.4/kbuild/.
>  
> -Note that unlike with Linux, and contrary to that document, you cannot
> -look at Kconfig files, or the default or generated config files etc.,
> -to find available configuration options.  This is because it is only
> -supported (and security supported) by the Xen Project, to change a
> -small subset of the options.  Attempts to change other options will be
> -silently overridden.  The only way to find which configuration options
> -are available is to run `make menuconfig' or the like.
> -
> -You can counter-override this behaviour by setting XEN_CONFIG_EXPERT=y
> -in your environment.  However, doing this is not supported and the
> -resulting configurations do not receive security support.  If you set
> -this variable there is nothing stopping you setting dangerously
> -experimental combinations of features - not even any warnings.
> +Only a subset of options is supported or security-supported by Xen
> +Project. You can explore all available options, including unsupported
> +ones and those recommended only for expert users, by using `make

"..., e.g. by using ..."

> +menuconfig` and enabling `CONFIG_UNSUPPORTED` and/or `CONFIG_EXPERT`.
> +However, enabling these options is not supported, and configurations
> +resulting from them do not receive security support.
>  
>  Options recognized by configure
>  ===============================

Jan