On 14/04/2025 6:55 pm, Marek Marczykowski-Górecki wrote: > On Mon, Apr 14, 2025 at 06:47:07PM +0100, Andrew Cooper wrote: >> On 14/04/2025 6:45 pm, Anthony PERARD wrote: >>> On Mon, Apr 14, 2025 at 12:09:03PM +0100, Andrew Cooper wrote: >>>> diff --git a/automation/gitlab-ci/build.yaml >>>> b/automation/gitlab-ci/build.yaml >>>> index 1b82b359d01f..ac5367874526 100644 >>>> --- a/automation/gitlab-ci/build.yaml >>>> +++ b/automation/gitlab-ci/build.yaml >>>> @@ -306,6 +306,7 @@ alpine-3.18-gcc-debug: >>>> CONFIG_ARGO=y >>>> CONFIG_UBSAN=y >>>> CONFIG_UBSAN_FATAL=y >>>> + CONFIG_UCODE_SCAN_DEFAULT=y >>> Is there a change >> DYM "chance" ? >> >>> that this patch series gets backported? Because that >>> new Kconfig option won't exist. >> Yes, I do intend to backport this whole series in due course, and yes, >> I'm aware. > A more backport-friendly way would be add ucode=scan to xen cmdline.
Yeah, but they're too long already IMO. Needing to override defaults to make our CI system useful is a good hint that the defaults are wrong. Same for console_timestamps, which isn't even deployed consistently across the testing. ~Andrew
