Hide Forgot
Description of problem: tuned should have the ability to add options to the kernel command line based on the defined profiles Steps to Reproduce: 1. Given a tuned profile that requests a kernel command line parameter e.g. intel_idle.max_cstate=0 Expected results: tuned should (using grubby or something similar) be able to edit the kernel command line to add/remove the specified kernel option.
Currently tuned allows changing the settings in the run time without reboot and this RFE will break this useful feature. Tuned now controls the max_cstate dynamically through the PM QOS interface which is very flexible. What will be the benefit to set it statically? In such case tuned will not be able to increase the max_cstate without reboot. This may also confuse users. Please note with grub2, editing the kernel command line is a pain. You need to patch the grub.cfg and also simultaneously edit the grub2 templates because you need to cover the case when the user regenerates the config with the grub2-mkconfig command. AFAIK this is currently not done by grubby. Is there any other use case than the intel_idle.max_cstate=0? Is it needed for custom profiles? In such case I could write such plugin, but I am against using this feature in the shipped profiles.
Jaroslav, As Jeremy has mentioned there are quite a few other parameters that would be nice if tuned could handle from a profile. the intel_idel.max_cstate=0 was simply an example.
Upstream commit adding this feature: https://git.fedorahosted.org/cgit/tuned.git/commit/?id=5b8a2d2e8e77ca502ed70da6db86ffe9eaae5076
If this Feature should be included in the 7.1 Release Notes, could you please change the Doc Type from Enhancement to "Release Note"? Note that the Release Notes are intended to list the most prominent and customer-relevant new features rather than every single enhancement. Cheers, Jirka
(In reply to Jiri Herrmann from comment #17) I think it doesn't need release note.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0550.html