| From: |
| "Rafael J. Wysocki" <rjw-AT-rjwysocki.net> |
| To: |
| Linux PM <linux-pm-AT-vger.kernel.org> |
| Subject: |
| [RFT][PATCH 0/3] cpufreq / PM: QoS: Introduce frequency QoS and use it in cpufreq |
| Date: |
| Wed, 16 Oct 2019 12:37:58 +0200 |
| Message-ID: |
| <2811202.iOFZ6YHztY@kreacher> |
| Cc: |
| Linux ACPI <linux-acpi-AT-vger.kernel.org>, LKML <linux-kernel-AT-vger.kernel.org>, Viresh Kumar <viresh.kumar-AT-linaro.org>, Sudeep Holla <sudeep.holla-AT-arm.com>, Dmitry Osipenko <digetx-AT-gmail.com> |
| Archive-link: |
| Article |
Hi All,
The motivation for this series is to address the problem discussed here:
https://lore.kernel.org/linux-pm/5ad2624194baa2f53acc1f1e...
and also reported here:
https://lore.kernel.org/linux-pm/20191015155735.GA29105@b...
Plus, generally speaking, using the policy CPU as a proxy for the policy
with respect to PM QoS does not feel particularly straightforward to me
and adds extra complexity.
Anyway, the first patch adds frequency QoS that is based on "raw" PM QoS (kind
of in analogy with device PM QoS) and is just about min and max frequency
requests (no direct relationship to devices).
The second patch switches over cpufreq and its users to the new frequency QoS.
[The Fixes: tag has been tentatively added to it.]
The third one removes frequency request types from device PM QoS.
Unfortunately, the patches are rather big, but also they are quite
straightforward.
I didn't have the time to test this series, so giving it a go would be much
appreciated.
Thanks,
Rafael
