On 10 October 2012 19:14, Sudeep KarkadaNagesha
wrote:
> Here is my understanding on this patch. This change is closely related
> to ACPI cpufreq driver(used mostly on Intel cores). This change was
> introduced to keep track of the related cpus as returned by ACPI
> firmware along with affected cp
On 10/10/12 14:26, Viresh Kumar wrote:
[...]
I couldn't understand the difference b/w h/w and s/w coordination. What
do we mean by them here.
Following patch added related related_cpu stuff:
commit e8628dd06d66f2e3965ec9742029b401d63434f1
Author: Darrick J. Wong
Date: Fri Apr 18 13:31:12 20
On 10 October 2012 17:31, Sudeep KarkadaNagesha
wrote:
> On 08/10/12 14:58, viresh kumar wrote:
>> affected_cpus(policy->cpus):
>> - List of CPUs that require software coordination of frequency.
>> - Processors part of affected_cpus share policy struct
>> - Policy limits the frequencies that the
Hi Viresh,
On 08/10/12 14:58, viresh kumar wrote:
Hi All,
Sorry for asking one of the most basic question of cpufreq :(
I couldn't get the difference between affected (policy->cpus) and
related cpus (policy->related_cpus) in cpufreq...
As per Documentation/code:
affected_cpus(policy->cpus):
Hi All,
Sorry for asking one of the most basic question of cpufreq :(
I couldn't get the difference between affected (policy->cpus) and
related cpus (policy->related_cpus) in cpufreq...
As per Documentation/code:
affected_cpus(policy->cpus):
- List of CPUs that require software coordination of
