From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antti P Miettinen Subject: Re: [PATCH 0/6] RFC: CPU frequency min/max as PM QoS params Date: Thu, 12 Jan 2012 10:43:49 +0200 Message-ID: <87ehv5cnui.fsf@amiettinen-lnx.nvidia.com> References: <1325810186-28986-1-git-send-email-amiettinen@nvidia.com> <87r4z6d784.fsf@amiettinen-lnx.nvidia.com> <201201120000.17044.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org "Rafael J. Wysocki" writes: > On Wednesday, January 11, 2012, Antti P Miettinen wrote: >> I think for CPU performance, it's probably simplest just to use >> frequency. Mapping from GOPS/MIPS/FLOPS/FPS is probably more sensily >> done by PM QoS client side. > > Well, unfortunately, frequency is kind of system-specific. I mean, > you need to know what frequencies are supported/available to use that, > so it would require the potential users to know the CPU internals. > > Thanks, > Rafael I would expect clients requesting for computing performance to require system specific knowledge anyway. Computing performance is often affected by target specific details (CPU, memory, interconnects). So something like board specific configuration parameters would probably be required for the PM QoS clients doing computing performance requests. --Antti