From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, andrew.cooper3@citrix.com,
george.dunlap@citrix.com, iwj@xenproject.org, jbeulich@suse.com,
julien@xen.org, wl@xen.org
Subject: [PATCH v4 0/2] introduce UNSUPPORTED
Date: Mon, 25 Jan 2021 13:27:38 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.2101251321420.20638@sstabellini-ThinkPad-T480s> (raw)
Hi all,
A recent thread [1] has exposed a couple of issues with our current way
of handling EXPERT.
1) It is not obvious that "Configure standard Xen features (expert
users)" is actually the famous EXPERT we keep talking about on xen-devel
2) It is not obvious when we need to enable EXPERT to get a specific
feature
In particular if you want to enable ACPI support so that you can boot
Xen on an ACPI platform, you have to enable EXPERT first. But searching
through the kconfig menu it is really not clear (type '/' and "ACPI"):
nothing in the description tells you that you need to enable EXPERT to
get the option.
This series makes things easier by doing the following:
- introduce a new kconfig option UNSUPPORTED which is clearly to enable
UNSUPPORTED features as defined by SUPPORT.md
- change EXPERT options to UNSUPPORTED where it makes sense: keep
depending on EXPERT for features made for experts
- tag unsupported features by adding (UNSUPPORTED) to the one-line
description
- clarify the EXPERT one-line description
[1] https://marc.info/?l=xen-devel&m=160333101228981
Cheers,
Stefano
Stefano Stabellini (2):
xen: EXPERT clean-up and introduce UNSUPPORTED
xen: add (EXPERT) to one-line descriptions when appropriate
xen/Kconfig | 11 ++++++++++-
xen/arch/arm/Kconfig | 10 +++++-----
xen/arch/x86/Kconfig | 8 ++++----
xen/common/Kconfig | 14 +++++++-------
xen/common/sched/Kconfig | 8 ++++----
5 files changed, 30 insertions(+), 21 deletions(-)
next reply other threads:[~2021-01-25 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 21:27 Stefano Stabellini [this message]
2021-01-25 21:27 ` [PATCH v4 1/2] xen: EXPERT clean-up and introduce UNSUPPORTED Stefano Stabellini
2021-01-26 9:22 ` Jan Beulich
2021-01-26 11:06 ` Bertrand Marquis
2021-01-26 11:11 ` Jan Beulich
2021-01-26 11:17 ` Bertrand Marquis
2021-01-26 13:08 ` Jan Beulich
2021-01-26 13:17 ` Ian Jackson
2021-01-26 13:19 ` Jan Beulich
2021-01-26 13:20 ` Bertrand Marquis
2021-01-26 15:18 ` Marek Marczykowski-Górecki
2021-01-26 15:23 ` Jan Beulich
2021-01-26 18:28 ` Stefano Stabellini
2021-01-26 13:51 ` Julien Grall
2021-01-26 14:23 ` Bertrand Marquis
2021-01-26 18:26 ` Stefano Stabellini
2021-01-25 21:27 ` [PATCH v4 2/2] xen: add (EXPERT) to one-line descriptions when appropriate Stefano Stabellini
2021-01-26 9:26 ` Jan Beulich
2021-01-26 18:36 ` Stefano Stabellini
2021-01-26 11:08 ` Bertrand Marquis
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=alpine.DEB.2.21.2101251321420.20638@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=wl@xen.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.