Re: [PATCH] cpufreq: Expose cpufreq coordination requirementsregardless of coordination mechanism

[Andrew Morton]

On Thu, 20 Mar 2008 17:43:54 -0700
"Darrick J. Wong" <djwong@xxxxxxxxxx> wrote:

> Currently, affected_cpus shows which CPUs need to have their frequency
> coordinated in software.  When hardware coordination is in use, the
> contents of this file appear the same as when no coordination is
> required.  This can lead to some confusion among user-space programs,
> for example, that do not know that extra coordination is required to
> force a CPU core to a particular speed to control power consumption.
> 
> To fix this, create a "related_cpus" attribute that always displays
> the coordination map regardless of whatever coordination strategy
> the cpufreq driver uses (sw or hw).  If the cpufreq driver does not
> provide a value, fall back to policy->cpus.

I was going to ding you for not updating the kernel->userspace API
documentation.  But it seems that none of this interface is documented
anyway :(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/