[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [RFC PATCH v1 0/1] ARCH_FIXED_CONFIG introduction for randconfig
Brief Overview: In the earlier patch series [1], it was introduced a comprehensive set of changes enabling a full Xen build for RISC-V. This early support primarily provides the minimum stubs required for the RISC-V Xen build. At this stage of development, many configs are deemed unnecessary and are expected to be disabled. Without ARCH_FIXED_CONFIG (or an alternative mechanism), the alternative is updating CI's build.yaml in multiple instances with the same configs, mirroring the approach taken in [1] to prevent the inadvertent activation of unsupported configs. For example, in scenarios like dom0less, we can exclude grant tables by setting "CONFIG_GRANT_TABLE=n" in ARCH_FIXED_CONFIG. This eliminates the need for intricate modifications to Kconfig configurations with conditions like "depends on X86 || ARM" or the introduction of HAS_* conditions followed by Kconfig updates with "depends on HAS_*," as illustrated in examples [2] or [3]. It might be useful for other architectures as well, especially for PPC, which is currently under development. There are several open questions: - Does introduction of ARCH_FIXED_CONFIG make sense? - Should ARCH_FIXED_CONFIG be re-used for *defconfig? [1] https://lore.kernel.org/xen-devel/b4e85f8f58787b4d179022973ce25673d6b56e36.1700761381.git.oleksii.kurochko@xxxxxxxxx/ [2] https://lore.kernel.org/xen-devel/cdc20255540a66ba0b6946ac6d48c11029cd3385.1701453087.git.oleksii.kurochko@xxxxxxxxx/ [3] https://lore.kernel.org/xen-devel/d42a34866edc70a12736b5c6976aa1b44b4ebd8a.1701453087.git.oleksii.kurochko@xxxxxxxxx/ Oleksii Kurochko (1): xen/Makefile: introduce ARCH_FIXED_CONFIG for randconfig xen/Makefile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) -- 2.43.0
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |