Skip to contentSkip to conversation

INSTALL: Mention kconfig

PATCH In review Ian Jackson 3 participants 3 messages Sep 21, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 INSTALL: Mention kconfig

Firstly, add a reference to the documentation for the kconfig system.

Secondly, warn the user about the XEN_CONFIG_EXPERT problem.

CC Doug Goldstein <[email protected]>
CC Wei Liu <[email protected]>
CC Jan Beulich <[email protected]>
CC Andrew Cooper <[email protected]>
---
 INSTALL | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
INSTALL +20 -0
index 9aa9ebdddc..62b0162864 100644
@@ -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.  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 overriden.  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 varible there is nothing stopping you setting dangerously
+experimental combinations of features - not even any warnings.
+
 Options recognized by configure
 ===============================
 
Signature · 7 lines
2.11.0


_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Acked-by on v1 1/1
#1 lore raw
Quoted 10 lines
Quoted 1 line
Quoted 1 line · On 21.09.18 at 16:56, <[email protected]> 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 <[email protected]>
CC Wei Liu <[email protected]>
CC Jan Beulich <[email protected]>
CC Andrew Cooper <[email protected]>

Fundamentally I'm fine with this, so in any event

I find the wording a little too negative though:

Quoted 5 lines
INSTALL +0 -0
@@ -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.

INSTALL following compile process. Once configure is done, make(1) has to be · line 30

Quoted 10 lines
INSTALL +9 -0
 
+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
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel

#2 lore raw
In reply to Ian Jackson

INSTALL following compile process. Once configure is done, make(1) has to be · line 38

Quoted 4 lines · Ian Jackson
INSTALL +4 -0
+
+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

Err... but we set XEN_CONFIG_EXPERT for shim build and shim is supported.

Wei.

Quoted 7 lines

+
Options recognized by configure
===============================

Signature · 1 line
2.11.0

_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel