[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1359976493.git.viresh.kumar@linaro.org>
Date: Mon, 4 Feb 2013 17:08:50 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: rjw@...k.pl
Cc: cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
robin.randhawa@....com, Steve.Bannister@....com,
Liviu.Dudau@....com, Viresh Kumar <viresh.kumar@...aro.org>
Subject: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
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
drivers/cpufreq/cpufreq.c | 41 ++++---
drivers/cpufreq/cpufreq_conservative.c | 142 +++++++++++++----------
drivers/cpufreq/cpufreq_governor.c | 140 +++++++++++++---------
drivers/cpufreq/cpufreq_governor.h | 42 ++++---
drivers/cpufreq/cpufreq_ondemand.c | 205 +++++++++++++++++++--------------
drivers/cpufreq/cpufreq_stats.c | 18 +--
drivers/cpufreq/cpufreq_userspace.c | 2 -
drivers/cpufreq/freq_table.c | 6 -
include/linux/cpufreq.h | 26 +----
9 files changed, 346 insertions(+), 276 deletions(-)
--
1.7.12.rc2.18.g61b472e
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists