From: Andrew Morton <akpm@linux-foundation.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org,
venkatesh.pallipadi@intel.com
Subject: Re: [PATCH] cpufreq: Expose cpufreq coordination requirements regardless of coordination mechanism
Date: Fri, 21 Mar 2008 15:41:24 -0700 [thread overview]
Message-ID: <20080321154124.668969a2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080321004354.GQ5529@tree.beaverton.ibm.com>
On Thu, 20 Mar 2008 17:43:54 -0700
"Darrick J. Wong" <djwong@us.ibm.com> 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 :(
next prev parent reply other threads:[~2008-03-21 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 0:43 [PATCH] cpufreq: Expose cpufreq coordination requirements regardless of coordination mechanism Darrick J. Wong
2008-03-21 22:41 ` Andrew Morton [this message]
2008-03-21 23:56 ` [PATCH] cpufreq: Document the currently undocumented parts of the sysfs interface Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080321154124.668969a2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=djwong@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox