[lkml]   [2008]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] cpufreq: Expose cpufreq coordination requirements regardless of coordination mechanism
On Thu, 20 Mar 2008 17:43:54 -0700
"Darrick J. Wong" <> 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 :(

 \ /
  Last update: 2008-03-21 23:45    [W:0.082 / U:0.240 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site