From: dmukhin@xen.org
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
andrew.cooper3@citrix.com, anthony.perard@vates.tech,
julien@xen.org, michal.orzel@amd.com, roger.pau@citrix.com,
dmukhin@ford.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] INSTALL: remove unsupported XEN_CONFIG_EXPERT from documentation
Date: Mon, 19 Jan 2026 23:10:50 -0800 [thread overview]
Message-ID: <aW8qesBTjzT4eZX3@kraken> (raw)
In-Reply-To: <6f275030-a3c2-4710-952e-56c3226b5a8b@suse.com>
On Mon, Jan 19, 2026 at 08:29:58AM +0100, Jan Beulich wrote:
> On 16.01.2026 21:47, Stefano Stabellini wrote:
> > On Fri, 16 Jan 2026, Jan Beulich wrote:
> >> On 16.01.2026 04:08, dmukhin@xen.org wrote:
> >>> --- a/INSTALL
> >>> +++ b/INSTALL
> >>> @@ -33,11 +33,11 @@ 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.
> >>
> >> I fear this earlier paragraph needs editing as well, which will then
> >> make more clear that ...
> >>
> >>> -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.
> >>> +This behavior can be overridden by enabling "Configure EXPERT features"
> >>> +in Kconfig (CONFIG_EXPERT).
> >>
> >> ... this may not be quite adequate.
> >>
> >
> > I am not sure how you would like to change the earlier paragraph or this
> > paragraph. I gave it a try and removed both paragraphs, replacing it
> > with this:
> >
> > """
> > 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.
> > """
> >
> > What do you think?
>
> This would be fine with me.
Thanks Stefano and Jan.
I will send an update shortly.
--
Denis
prev parent reply other threads:[~2026-01-20 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 3:08 [PATCH v2] INSTALL: remove unsupported XEN_CONFIG_EXPERT from documentation dmukhin
2026-01-16 7:04 ` Jan Beulich
2026-01-16 20:47 ` Stefano Stabellini
2026-01-19 7:29 ` Jan Beulich
2026-01-20 7:10 ` dmukhin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aW8qesBTjzT4eZX3@kraken \
--to=dmukhin@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.