Re: [tip: x86/urgent] x86/config: Make the x86 defconfigs a bit more usable

[Ingo Molnar <mingo@kernel.org>]

* Peter Zijlstra <peterz@infradead.org> wrote:

> On Thu, Mar 24, 2022 at 08:50:16AM -0000, tip-bot2 for Ingo Molnar wrote:
> > The following commit has been merged into the x86/urgent branch of tip:
> > 
> > Commit-ID:     aee8bf2d5aab5e7cc24fa90238930fd14d72e580
> > Gitweb:        https://git.kernel.org/tip/aee8bf2d5aab5e7cc24fa90238930fd14d72e580
> > Author:        Ingo Molnar <mingo@kernel.org>
> > AuthorDate:    Thu, 24 Mar 2022 09:31:13 +01:00
> > Committer:     Ingo Molnar <mingo@kernel.org>
> > CommitterDate: Thu, 24 Mar 2022 09:32:20 +01:00
> > 
> > x86/config: Make the x86 defconfigs a bit more usable
> > 
> >  - Use 'make savedefconfig' to refresh & regenerate the files
> >  - Add in KVM boot enablers
> 
> We shouldn't duplicate kvm_guest.config.

I think x86-defconfig should be usable by itself - not just via the 
somewhat obscure combination of:

  make defconfig
  make kvm_guest.config

right?

> >  - Enable the cgroup features most distros rely on
> 
> I've not yet had defconfig+kvm_guest.config fail to boot on debian
> images (I occasionally grab one here:
> https://cloud.debian.org/images/cloud/sid/daily/latest/ )

Systemd is rather negative about missing cgroup features - at a point it 
used to insert 30(?) seconds delays during bootup warning about missing 
cgroups support, etc.

Also the main Debian derived distros (Ubuntu, etc.) plus Debian itself has 
most of cgroups enabled - so why should we test something that very few 
users are using?

Thanks,

	Ingo