From: "Eugeny S. Mints" <eugeny.mints@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Eugeny S. Mints" <eugeny.mints@gmail.com>,
pm list <linux-pm@lists.osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH] PowerOP, PowerOP Core, 1/2
Date: Mon, 18 Sep 2006 23:58:04 +0400 [thread overview]
Message-ID: <450EFA4C.1070004@gmail.com> (raw)
In-Reply-To: <450E83DC.4050503@gmail.com>
Eugeny S. Mints wrote:
> Pavel Machek wrote:
>> Hi!
>>
[skip]
>> How is it going to work on 8cpu box? will
>> you have states like cpu1_800MHz_cpu2_1600MHz_cpu3_800MHz_... ?
basically I guess you are asking about what the names of operating points are
and how to distinguish between operating points from userspace on 8cpu box.
An advantage of PowerOP approach is that operating point name is used as a
_handle_ and may or may not be meaningful. The idea is that if a policy manager
needs to make a decision and needs to distinguish between operating points it
can check value of any power parameters of operating points in question. Power
parameter values may be obtained under <op_name> dir name.
With such approach a policy manger may compare operating points at runtime and
should not rely on compile time knowledge about what name corresponds to what
set of power parameter values. It uses name as a handle.
Eugeny
>
> i do not operate with term 'state' so I don't understand what it means
> here.
>
> Eugeny
>
>> Pavel
>
>
next prev parent reply other threads:[~2006-09-18 19:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 14:37 [PATCH] PowerOP, PowerOP Core, 1/2 Eugeny S. Mints
2006-09-18 10:44 ` [linux-pm] " Pavel Machek
2006-09-18 11:32 ` Eugeny S. Mints
2006-09-18 19:58 ` Eugeny S. Mints [this message]
2006-09-18 20:07 ` Vitaly Wool
2006-09-19 18:22 ` Pavel Machek
2006-09-18 13:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 19:46 [linux-pm] " Scott E. Preece
2006-09-19 20:06 ` Eugeny S. Mints
2006-09-22 14:09 ` Pavel Machek
2006-09-26 21:45 ` Matthew Locke
2006-09-19 21:37 Scott E. Preece
2006-09-22 14:11 ` Pavel Machek
2006-09-22 14:48 ` Igor Stoppa
2006-09-22 20:28 Scott E. Preece
2006-09-22 21:18 ` Vitaly Wool
2006-09-22 20:34 Scott E. Preece
2006-09-23 11:18 ` Pavel Machek
2006-09-24 21:33 ` Matthew Locke
2006-09-24 21:45 ` Pavel Machek
2006-09-22 21:10 Woodruff, Richard
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=450EFA4C.1070004@gmail.com \
--to=eugeny.mints@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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