firmware/shim: UNSUPPORTED=n
authorJan Beulich <jbeulich@suse.com>
Thu, 27 May 2021 12:39:33 +0000 (14:39 +0200)
committerJan Beulich <jbeulich@suse.com>
Thu, 27 May 2021 12:39:33 +0000 (14:39 +0200)
commitb509d4a688d80e802ff580990288ef5e17859df6
treee2960c45a47a2864702ab269fad175726efbf803
parent7c110dd335a17be52549dc4b9dfbfba8165ade40
firmware/shim: UNSUPPORTED=n

We shouldn't default to include any unsupported code in the shim. Mark
the setting as off, replacing the ARGO specification. This points out
anomalies with the scheduler configuration: Unsupported schedulers
better don't default to Y in release builds (like is already the case
for ARINC653). Without at least the SCHED_NULL adjustments, the shim
would suddenly build with RTDS as its default scheduler.

As a result, the SCHED_NULL setting can also be dropped from defconfig.

Clearly with the shim defaulting to it, SCHED_NULL must be supported at
least there.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Dario Faggioli <dfaggioli@suse.com>
SUPPORT.md
xen/arch/x86/configs/pvshim_defconfig
xen/common/sched/Kconfig