<div dir="auto"><div>As is, this looks fine for lunar kernel.</div><div dir="auto"> </div><div dir="auto">Or even add KVM flavour to config generator in unstable kernel, like we have RISCV there. Such that we split configs for it in the parent kernel by default.</div><div dir="auto"> <div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Thu, 27 Oct 2022, 12:54 Stefan Bader, <<a href="mailto:stefan.bader@canonical.com">stefan.bader@canonical.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 27.10.22 10:41, Paolo Pisati wrote: > BugLink: <a href="https://bugs.launchpad.net/bugs/1994693" rel="noreferrer noreferrer" target="_blank">https://bugs.launchpad.net/bugs/1994693</a> > > [Issue] > > linux-kvm wasn't using annotations from debian.master, and that induced a > skew in fundamental config options between main and kvm kernels. > > [Fix] > > The attached series (broken down in pieces to ease review) make linux-kvm use > annotations from debian.master and override options that are meant to be > different. > > Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config] > Update SQUASHFS configs" already posted on the mailing list. > > [How to test] > > Crank updateconfigs shouldn't report any check-config error afterward. > > [Regression potential] > > These five patches: > > UBUNTU: [Config] align IMA config with debian.master > UBUNTU: [Config] align UBSAN config with debian.master > UBUNTU: [Config] disable X86_KERNEL_IBT > UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master > UBUNTU: [Config] align LSM with master > > are the only changes in kvm config, everything else is annotations fix up. > > Paolo Pisati (14): > UBUNTU: [Config] align IMA config with debian.master > UBUNTU: annotations: include annotations from debian.master > UBUNTU: annotations: CONFIG_SND_SOC* policy is not available > UBUNTU: annotations: fix up disabled options in master but not > available in kvm > UBUNTU: annotations: fix up options built as module in master but not > available in kvm > UBUNTU: annotations: fix up options built-in in master but not > available in kvm > UBUNTU: [Config] align UBSAN config with debian.master > UBUNTU: annotations: fix up options built-in in master but disabled in > kvm > UBUNTU: annotations: fix up options built as module in master but > disabled in kvm > UBUNTU: annotations: fix up options built-in in master but built as > module in kvm > UBUNTU: [Config] disable X86_KERNEL_IBT > UBUNTU: annotations: fix up LATENCYTOP > UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master > UBUNTU: [Config] align LSM with master > > debian.kvm/config/annotations | 61 ++++++++++++++++++++++++++ > debian.kvm/config/config.common.ubuntu | 57 +++++++++++++++++++++--- > 2 files changed, 111 insertions(+), 7 deletions(-) > First two complaints are more nitpick but anyway: this should at least include a pull request. Second, "K/linux-kvm" is bad because "/" is more commonly used to list all required pieces. Please use "K:linux-kvm" or the complete handle "kinetic:linux-kvm". My main concern is with the patches which change config. There is no explanation in the commit message why this makes sense/is done. The initial approach of KVM was a minimal kernel which quickly boots in a VM/cloud. I know this all should have been done better that way when this thing was created. But at least now with changing things to match master we should better note down (and the best long-term place is the commit message) what these things do and why we think this should be synced now. -Stefan -- kernel-team mailing list <a href="mailto:kernel-team@lists.ubuntu.com" target="_blank" rel="noreferrer">kernel-team@lists.ubuntu.com</a> <a href="https://lists.ubuntu.com/mailman/listinfo/kernel-team" rel="noreferrer noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kernel-team</a> </blockquote></div></div></div>