RFC allow overriding default preempt mode from command line
Get series with b4
b4 am [email protected]Versions newest first
- v2 RFC Latest5 patches 6 repliesIn review
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | jump_label: split out declaration parts into its own headersinclude/ include/ | +50 | 0 replies | |
| 2/5 | kernel: allow to configure PREEMPT_NONE, PREEMPT_VOLUNTARY on kernel command lineDocumentation/ include/ include/ +1 more | +47 | 0 replies | |
| 3/5 | kernel: ARCH_NO_PREEMPT shouldn't exclude PREEMPT_VOLUNTARYkernel/ | +0 | 0 replies | |
| 4/5 | kernel: introduce CONFIG_PREEMPT_DYNAMICinclude/ include/ kernel/ +1 more | +42 | 0 replies | |
| 5/5 | kernel: drop PREEMPT_NONE compile time optionkernel/ | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [RFC PATCH v2 0/5] allow overriding default preempt mode from command line
Hi,
let me repost the pile that has grown from the initial patch based on the review feedback I have collected from Peter. I do realize that he also suggested to go from the other direction and implement this for the full preemption mode first. As I've said I believe this would require to examine all CONFIG_PREEMPTION code paths and preempt_mode=[none,voluntary] is already quite useful for distributions which are targeting high throuhput and desktop environments. Adding full preemption on top is definitely desirable and something we will be looking into. This is the first step in that direction.
If maintainers really believe that starting from the full preemption mode first then we are willing to explore that path of course.
I am stil posting that as an RFC because I didn't get to push this through a complete compile time testing and rely on 0-day bot in that aspect.
Thanks and I am looking forward for a further feedback.