Message ID | cover.1550748118.git.viresh.kumar@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | cpufreq: Use QoS layer to manage freq-constraints | expand |
On Thursday, February 21, 2019 12:29:26 PM CET Viresh Kumar wrote: > Hello, > > This patchset attempts to manage CPU frequency constraints using the PM > QoS framework. It only does the basic stuff right now and moves the > userspace constraints to use the QoS infrastructure. > > Todo: > - Migrate all users to the QoS framework and get rid of cpufreq specific > notifiers. > - Make PM QoS learn about the relation of CPUs in a policy, so a single > list of constraints is managed for all of them instead of per-cpu > constraints. > > V1->V2: > - The previous version introduced a completely new framework, this one > moves to PM QoS instead. > - Lots of changes because of this. Well, thanks for working on this, but I'm rather unlikely to look at it in detail before 5.1-rc1 is released. Cheers, Rafael
On 21-02-19, 12:30, Rafael J. Wysocki wrote: > On Thursday, February 21, 2019 12:29:26 PM CET Viresh Kumar wrote: > > Hello, > > > > This patchset attempts to manage CPU frequency constraints using the PM > > QoS framework. It only does the basic stuff right now and moves the > > userspace constraints to use the QoS infrastructure. > > > > Todo: > > - Migrate all users to the QoS framework and get rid of cpufreq specific > > notifiers. > > - Make PM QoS learn about the relation of CPUs in a policy, so a single > > list of constraints is managed for all of them instead of per-cpu > > constraints. > > > > V1->V2: > > - The previous version introduced a completely new framework, this one > > moves to PM QoS instead. > > - Lots of changes because of this. > > Well, thanks for working on this, but I'm rather unlikely to look at it in > detail before 5.1-rc1 is released. Ping!
On 21-02-19, 12:30, Rafael J. Wysocki wrote: > On Thursday, February 21, 2019 12:29:26 PM CET Viresh Kumar wrote: > > Hello, > > > > This patchset attempts to manage CPU frequency constraints using the PM > > QoS framework. It only does the basic stuff right now and moves the > > userspace constraints to use the QoS infrastructure. > > > > Todo: > > - Migrate all users to the QoS framework and get rid of cpufreq specific > > notifiers. > > - Make PM QoS learn about the relation of CPUs in a policy, so a single > > list of constraints is managed for all of them instead of per-cpu > > constraints. > > > > V1->V2: > > - The previous version introduced a completely new framework, this one > > moves to PM QoS instead. > > - Lots of changes because of this. > > Well, thanks for working on this, but I'm rather unlikely to look at it in > detail before 5.1-rc1 is released. Hi Rafael, This series was posted almost 3 months back. Any comments on this would be very helpful.