-
Notifications
You must be signed in to change notification settings - Fork 77
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
PREEMPT_RT detection on kernel 6.12 #257
Comments
Hello @alexswerner! Thanks for raising this issue. I've tried a different approach in PR: #260. Do you think this will solve the issue?. If the changes look good to you, do you mind testing it and approving the PR. Thank you! |
Hi @saikishor , I think your approach in general makes sense. I've ask the rt-users mailing list what their perspective on this is but didn't get a response (https://lore.kernel.org/linux-rt-users/70b66c69bdd3d4cf8dd7a7f17051b074b9fbcf48.camel@alexanderwerner.net/T/#u) . Maybe the lkml is actually to discuss this question. |
@alexswerner Thanks for the response. I believe the above one should detect the RT kernel without issues. I would say this is a better approach than the earlier one, as the uname always has this information. Thank you. |
Hi,
to see how things go when using a mainline kernel which has most of the PREEMPT_RT patch merged I'm trying kernel version 6.12. However, the realtime_tools does not detect that it is a kernel with PREEMPT_RT:
The detection happens in
realtime_tools/src/realtime_helpers.cpp
Line 46 in 5b85370
/sys/kernel/realtime
. This file does not exists in a 6.12 kernel with PREEMPT_RT activated. Other have noticed this as well: https://forum.linuxcnc.org/38-general-linuxcnc-questions/54542-real-time-kerel-not-detected-on-patched-6-12?start=40 . In that thread people point out that this patch creates the file:https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/commit/?h=linux-6.12.y-rt-rebase&id=3e7545de923c4e8184c2be0b95341fdc7ef1c193 . This has not been merged for now (v6.13-rc7).
The text was updated successfully, but these errors were encountered: