-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add FCOS variant to use rt-kernel now that PREEMPT_RT is merged into 6.12 #1843
Comments
I think this probably makes most sense to discuss in the context of #1726. Having multiple FCOS variants adds a lot of complexity unfortunately. One approach is to provide the definitions for it like centos-bootc does and let users build it themselves with That said, for now, it should also work to use |
I think that could be related : https://bugzilla.redhat.com/show_bug.cgi?id=2329409 |
My understanding is that now that it's merged in the upstream kernel, once https://bugzilla.redhat.com/show_bug.cgi?id=2329409 is enabled, there will be a single kernel build and the real time part would be enabled with a kernel argument likely, so there would be nothing for us to do here to have it. |
Reading https://www.kernelconfig.io/CONFIG_PREEMPT_RT?q=PREEMPT_RT&kernelversion=6.12.1&arch=x86, maybe it's not the case yet and Fedora will have to build two kernels to get it. |
Yes, it is merged into the kernel. But my understanding is that it is a compile time switch and not a boot time switch. So it would require two separate built kernels. |
This might require a Fedora Change proposal to get the |
Describe the enhancement
I would like to be able to use FCOS with kernel compiled with the RT patches (PREEMPT_RT) now that this is merged into the mainline kernel (but still require to be compiled with the proper config) to better support latency critical applications.
System details
This would only be feasible once FCOS starts to ship with kernel 6.12 - I don't expect to have any external patches applied.
Additional information
No response
The text was updated successfully, but these errors were encountered: