Re: [Xen-devel] [PATCH] INSTALL: Mention kconfig

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 21.09.18 at 16:56, <ian.jackson@xxxxxxxxxx> wrote:
> Firstly, add a reference to the documentation for the kconfig system.
> 
> Secondly, warn the user about the XEN_CONFIG_EXPERT problem.
> 
> CC: Doug Goldstein <cardoe@xxxxxxxxxx>
> CC: Wei Liu <wei.liu2@xxxxxxxxxx>
> CC: Jan Beulich <jbeulich@xxxxxxxx>
> CC: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxx>

Fundamentally I'm fine with this, so in any event
Acked-by: Jan Beulich <jbeulich@xxxxxxxx>
I find the wording a little too negative though:

> --- a/INSTALL
> +++ b/INSTALL
> @@ -19,6 +19,26 @@ following compile process. Once configure is done, make(1) 
> has to be
>  called. Also make(1) recognizes certain arguments. The following sections
>  will give an overview.
>  
> +Xen Hypervisor
> +==============
> +
> +Xen itself is configured via a `kconfig' system borrowed from Linux.
> +See docs/misc/kconfig.txt.
> +
> +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.

I don't think looking at Kconfig files to find available options gives any
better or worse results than for Linux. If you take a global view, you'll
find the expert (and environment variable) dependency. If you look
at particular Kconfig files, what you see as available (for choice) might
not actually be due to other dependencies and/or selects. It's just that
for Xen that vast majority of options is unavailable by default, while
for Linux it's for comparatively a much smaller subset.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel