# Why did 6.1 longterm branch change the CONFIG\_PREEMPT setting?

**URL:** <https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [October 14, 2023, 2:05pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711 "2023-10-14T14:05:54Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\
**Post date:** [October 14, 2023, 2:05pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/1 "2023-10-14T14:05:54Z")

</div>

I found that the linux-lts kernel (6.1 longterm branch) has different preemption settings than the following and previous kernels.

package linux-lts has:

```auto
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set

```

package linux has:

```auto
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y

```

And it looks like that this change was made specifically for the LTS kernel when it became LTS.

> **[move to 6.1 longterm branch (1e57554f) · Commits · Arch Linux / Packaging /...](https://gitlab.archlinux.org/archlinux/packaging/packages/linux-lts/-/commit/1e57554f760c458ae0a37f1ef0ae677f397ad4dd)**
>
> \- sync config with Arch mainline kernel package - set CONFIG\_PREEMPT\_VOLUNTARY as new default - PREEMPT\_DYNAMIC is now available and desired behavior can be choosen using kernel append line -...

What is the reason for this? Will this change also be made to the 6.5 or 6.6 kernel when it becomes the next LTS?

---

<div class="post-metadata">

**Author:** ![BS86](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/bs86/32/18119_2.png) [@BS86](https://forum.endeavouros.com/u/BS86)\
**Post date:** [October 14, 2023, 3:07pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/2 "2023-10-14T15:07:16Z")

</div>

> [@mbod](#):
>
> What is the reason for this?

from the link you posted:

```auto
- set CONFIG_PREEMPT_VOLUNTARY as new default - PREEMPT_DYNAMIC is now available
  and desired behavior can be choosen using kernel append line

```

as there is no issue mentioned, I guess that’s all the information that is available.

> [@mbod](#):
>
> Will this change also be made to the 6.5 or 6.6 kernel when it becomes the next LTS?

6.5 won’t be the new LTS. 6.6 could theoretically become a LTS kernel, but so could 6.7.  
For that and for the remaining question:

> [@Updating/moving packages to -5 names](https://forum.endeavouros.com/t/updating-moving-packages-to-5-names/46154/5):
>
> I am sorry but the crystal ball is currently broken. No way to tell the future.

---

<div class="post-metadata">

**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\
**Post date:** [October 14, 2023, 3:10pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/3 "2023-10-14T15:10:37Z")

</div>

> [@BS86](#):
>
> as there is no issue mentioned, I guess that’s all the information that is available.

I found this link and I read it and it gives no reason why the settings fo an LTsSkernel are different. The previous kernels and the following kernels all have

```auto
CONFIG_PREEMPT_VOLUNTARY not set

```

I was asking this question here because we have experts in the forum who are closer to the Arch devs or kernel devs. And they may know more about the topic. But thank you for your contribution.

---

<div class="post-metadata">

**Author:** ![Stagger\_Lee](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stagger_lee/32/93385_2.png) [@Stagger\_Lee](https://forum.endeavouros.com/u/Stagger_Lee)\
**Post date:** [October 14, 2023, 3:14pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/4 "2023-10-14T15:14:13Z")

</div>

See [here](https://bugs.archlinux.org/task/75456?project=1&string=linux-lts&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=closed&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&order=lastedit&sort=desc). This was not able to be inplemented in kernel 5.15 but was enabled with 6.1 - the logic being “Enabling CONFIG\_PREEMPT\_DYNAMIC=y is a clear all around benefit allowing system administrators to choose the best mode for their use case [from the kernel config line].”

---

<div class="post-metadata">

**Author:** ![BS86](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/bs86/32/18119_2.png) [@BS86](https://forum.endeavouros.com/u/BS86)\
**Post date:** [October 14, 2023, 3:29pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/5 "2023-10-14T15:29:33Z")

</div>

> [@mbod](#):
>
> why the settings fo an LTsSkernel are different.

6.1 when it was `linux` did not change that setting:

> **[6.1.arch1-1 (c15fb537) · Commits · Arch Linux / Packaging / Packages / linux...](https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/commit/c15fb537c558709f3baa8da9d9adc0e36398fecb)**
>
> GitLab Enterprise Edition

> [@mbod](#):
>
> The previous kernels and the following kernels all have

you are expecting something that simply is not there. The LTS kernel is maintained by a completely different maintainer than the other two official kernels. Therefore, they also follow different philosophies and configs.  
Maintainers of the regular kernel:  
[Jan Alexander Steffens](https://archlinux.org/packages/?maintainer=heftig)  
[David Runge](https://archlinux.org/packages/?maintainer=dvzrv)  
[Tobias Powalowski](https://archlinux.org/packages/?maintainer=tpowa)  
[Levente Polyak](https://archlinux.org/packages/?maintainer=anthraxx)

Maintainer of the Zen-Kernel:  
[Jan Alexander Steffens](https://archlinux.org/packages/?maintainer=heftig)  
[David Runge](https://archlinux.org/packages/?maintainer=dvzrv)  
Although both are practically exclusively maintained by Heftig.

LTS Kernel Maintainer:  
[Andreas Radke](https://archlinux.org/packages/?maintainer=andyrtr)

> [@Stagger\_Lee](#):
>
> See [here](https://bugs.archlinux.org/task/75456?project=1&string=linux-lts&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=closed&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&order=lastedit&sort=desc). This was not able to be inplemented in kernel 5.15 but was enabled with 6.1 - the logic being “Enabling CONFIG\_PREEMPT\_DYNAMIC=y is a clear all around benefit allowing system administrators to choose the best mode for their use case [from the kernel config line].”

the LTS kernel maintainer clearly sees that as a valid reason to change the default for the LTS kernel, while the other maintainers don’t see the necessity (or no one raised that issue for the other kernels).

---

<div class="post-metadata">

**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\
**Post date:** [October 14, 2023, 3:58pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/6 "2023-10-14T15:58:33Z")

</div>

> [@Stagger\_Lee](#):
>
> See [here](https://bugs.archlinux.org/task/75456?project=1&string=linux-lts&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=closed&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&order=lastedit&sort=desc). This was not able to be inplemented in kernel 5.15 but was enabled with 6.1 - the logic being “Enabling CONFIG\_PREEMPT\_DYNAMIC=y is a clear all around benefit allowing system administrators to choose the best mode for their use case [from the kernel config line].”

This is an interesting read. Thank you for the link. Although the comments on this page are not making things clearer.

The maintainer Andreas Radke is saying:

> And default CONFIG\_PREEMPT=y (low latency desktop) is not desired for LTS kernels.

How come? I would say that this is an opinion based on the assumption that LTS kernels are for servers. And servers dont want `CONFIG_PREEMPT=y`. Well, that is debatable.

Anyways, I find it very confusing that an official arch kernel is changing the config if it is moving from linux to linux-lts. That does not make sense to me. A server admin can easily change the preemption on the kernel commandline, thanks to `CONFIG_PREEMPT_DYNAMIC=y`, but all the arch desktop users should not need to do that. In fact I am pretty sure that they do not even know that they have to do that to get the same system responsiveness as always.

---

<div class="post-metadata">

**Author:** ![keybreak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/keybreak/32/9257_2.png) [@keybreak](https://forum.endeavouros.com/u/keybreak)\
**Post date:** [October 14, 2023, 4:01pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/7 "2023-10-14T16:01:07Z")

</div>

> [@mbod](#):
>
> How come? I would say that this is an opinion based on the assumption that LTS kernels are for servers. And servers dont want `CONFIG_PREEMPT=y`. Well, that is debatable.

Not sure that’s the reason, but if it is…I’m not a server, yet i want it for my lts kernel! 🤣

---

<div class="post-metadata">

**Author:** ![Stagger\_Lee](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stagger_lee/32/93385_2.png) [@Stagger\_Lee](https://forum.endeavouros.com/u/Stagger_Lee)\
**Post date:** [October 14, 2023, 4:01pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/8 "2023-10-14T16:01:59Z")

</div>

> [@mbod](#):
>
> I would say that this is an opinion based on the assumption that LTS kernels are for servers.

I would say that’s probably correct - or rather, LTS kernels are probably more likely to be the kernel used on servers.

> [@mbod](#):
>
> Well, that is debatable.

Well, yeah 😄.

> [@mbod](#):
>
> …all the arch desktop users should not need to do that. In fact I am pretty sure that they do not even know

![bingo_new](https://forum.endeavouros.com/uploads/default/original/3X/9/0/90b04bce63f9e798e29ff5d0efc97276936bb891.gif)

---

<div class="post-metadata">

**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\
**Post date:** [October 14, 2023, 4:18pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/9 "2023-10-14T16:18:18Z")

</div>

ok. so that leaves me with another question then.

If I add to the kernel comandline of the lts kernel `preempt=full`

How can I tell that the setting is active and not just sillently ignored? I gave it a try but I do not see any hint in the journal that preemption has changed. How can I check that?

EDIT:

I found the answer:

```auto
cat /sys/kernel/debug/sched/preempt
none voluntary (full)

```

---

<div class="post-metadata">

**Author:** ![keybreak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/keybreak/32/9257_2.png) [@keybreak](https://forum.endeavouros.com/u/keybreak)\
**Post date:** [October 14, 2023, 4:44pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/10 "2023-10-14T16:44:06Z")

</div>

Thx for mentioning all that, kinda big deal for it to get unnoticed…

![honka_animated-128px-46](https://forum.endeavouros.com/uploads/default/original/3X/6/e/6ec70ef6c3a3daed535ee074a8ce586ae940896e.gif)

---

<div class="post-metadata">

**Author:** ![BS86](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/bs86/32/18119_2.png) [@BS86](https://forum.endeavouros.com/u/BS86)\
**Post date:** [October 14, 2023, 5:28pm UTC](https://forum.endeavouros.com/t/why-did-6-1-longterm-branch-change-the-config-preempt-setting/46711/11 "2023-10-14T17:28:32Z")

</div>

> [@mbod](#):
>
> Anyways, I find it very confusing that an official arch kernel is changing the config if it is moving from linux to linux-lts.

well …

> [@BS86](#):
>
> you are expecting something that simply is not there. The LTS kernel is maintained by a completely different maintainer than the other two official kernels. Therefore, they also follow different philosophies and configs.

that is the only guideline that all Arch maintainers have to follow, and it is rather vague:  
[https://wiki.archlinux.org/title/Arch\_package\_guidelines](https://wiki.archlinux.org/title/Arch_package_guidelines)
