[lkml]   [2013]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
On Monday, February 04, 2013 05:08:50 PM Viresh Kumar wrote:
> Currently, there can't be multiple instances of single governor_type. If we have
> a multi-package system, where we have multiple instances of struct policy (per
> package), we can't have multiple instances of same governor. i.e. We can't have
> multiple instances of ondemand governor for multiple packages.
> Governors directory in sysfs is created at /sys/devices/system/cpu/cpufreq/
> governor-name/. Which again reflects that there can be only one instance of a
> governor_type in the system.
> This is a bottleneck for multicluster system, where we want different packages
> to use same governor type, but with different tunables.
> This patchset is inclined towards fixing this issue.
> Viresh Kumar (4):
> cpufreq: Don't check cpu_online(policy->cpu)
> cpufreq: stats: Get rid of CPUFREQ_STATDEVICE_ATTR
> cpufreq: Add per policy governor-init/exit infrastructure
> cpufreq: governor: Implement per policy instances of governors

Well, [1-2/4] are things I can take for v3.9 no problem. The other two I'd
wait for the next cycle to be honest. We already have 30+ cpufreq patches
scheduled for v3.9 and some of them quite subtle for that matter.


I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

 \ /
  Last update: 2013-02-04 14:46    [W:0.197 / U:1.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site