Adding pm_qos_resume_latency_us option for cpu plugin.

[CZerta]

Resolves: rhbz#2118786

Signed-off-by: Jan Zerdik [email protected]

[CZerta]

@joemario Should we disable dynamic tuning similarly as it is dissabled with force_latency option?

[yarda]

@joemario Should we disable dynamic tuning similarly as it is dissabled with force_latency option?

Dynamic tuning is disabled in RHEL. If enabled, it dynamically changes the global PM QoS according to the CPU load. I think it should work per CPU plugin instance. I.e. instead of the global PM QoS each plugin instance should dynamically change the PM QoS just for the CPUs in the instance. If the PM QoS is set explicitly for the instance, the instance shouldn't perform the dynamic tuning.

[joemario]

Thank you Jaroslav for the info on dynamic tuning. I was unaware of those details.