From b8092f9c188e4394f136784f881528268895b6ab Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Fri, 21 Sep 2018 15:40:19 +0100 Subject: [PATCH] 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 CC: Wei Liu CC: Jan Beulich CC: Andrew Cooper Signed-off-by: Ian Jackson --- INSTALL | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/INSTALL b/INSTALL index 9aa9ebdddc..62b0162864 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 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 =============================== -- 2.30.2