From: Ian Jackson Date: Fri, 21 Sep 2018 14:40:19 +0000 (+0100) Subject: INSTALL: Mention kconfig X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=1cd55de7bdef3e78ed4b015b51dd5d3a241c0213;p=people%2Fiwj%2Fxen.git 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: Wei Liu CC: Andrew Cooper CC: Jan Beulich Signed-off-by: Ian Jackson Reviewed-by: Doug Goldstein --- v2: Fix typos --- diff --git a/INSTALL b/INSTALL index 9aa9ebdddc..e28348509f 100644 --- 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. 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. + Options recognized by configure ===============================