CONFIG_PREEMPT changes from 6.6.9 to 6.6.10 about linux-tkg HOT 3 CLOSED

The reason is rather simple: we use Arch's base config file as starting point. And we keep on following the kernel's config file when the kernel becomes lts. And the config differ when the transfer is done for a reason I ignore:

https://gitlab.archlinux.org/archlinux/packaging/packages/linux-lts/-/blob/42324ac498fe636cfce193add03da2fd36c82ca0/config

https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/2db49d4fbcda88d76a4c236ccb5a7986715d70ba/config

from linux-tkg.

I do agree that it's confusing and possibly undesirable, but indeed it's only due to pulling arch defconfig updates. We should make the PREEMPT config only bound to our own options instead of relying onto the defconfig alone for default settings.

from linux-tkg.

This is what I thought. I believe the Arch behaviour is wrong. It does not make sense to change the config just because a certain kernel release is now LTS.

Anyways, for all those who want to keep the same user experience for all kernels I recommend kernel cmdline option preempt=full. This is the default kernel setting for the current Arch kernel releases and the cmdline option ensures that all LTS kernels keep that setting as well.

Or, may be, linux-tkg can add preempt=full as part of the _custom_commandline=""

from linux-tkg.