Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Subject: Re: [PATCH 0/2] Ignore Energy Model with abstract scale in IPA and
 DTPM
To:     Daniel Lezcano <daniel.lezcano@linaro.org>
Cc:     amit.kachhap@gmail.com, viresh.kumar@linaro.org, rafael@kernel.org,
        amitk@kernel.org, rui.zhang@intel.com, dietmar.eggemann@arm.com,
        Pierre.Gondois@arm.com, linux-kernel@vger.kernel.org,
        linux-pm@vger.kernel.org
References: <20220207073036.14901-1-lukasz.luba@arm.com>
 <0d2217e0-44f7-8587-3e1f-a73d301ab166@linaro.org>
From:   Lukasz Luba <lukasz.luba@arm.com>
Message-ID: <616307f7-b419-8e36-6879-6cf6f4e02d5a@arm.com>
Date:   Mon, 7 Feb 2022 11:44:44 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <0d2217e0-44f7-8587-3e1f-a73d301ab166@linaro.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2/7/22 10:41 AM, Daniel Lezcano wrote:
> On 07/02/2022 08:30, Lukasz Luba wrote:
>> Hi all,
>>
>> The Energy Model supports abstract scale power values. This might cause
>> issues for some mechanisms like thermal governor IPA or DTPM, which
>> expect that all devices provide sane power values. This patch set 
>> prevents
>> from registering such devices for IPA and DTPM.
> 
> 
> Does it mean for example big and little have both 0-100 ?
> 
> 

Unfortunately, these can be any numbers. I hope at least the CPUs
Big and Little power have sense: Little power is not higher
than Big power. The purpose of EM is to enable EAS, so this power
relation between Big and Little should have sense. Someone
who is not willing to or cannot expose real power values, still
wants the EAS to operate (my assumption and hope). The SCMI FW can
provide abstract power values. It's in the SCMI spec. Thus,
creating these abstract scale power values for big.LITTLE the right
way should result in properly working EAS.

I can also have hope for GPU vs. Big power, but it is a weaker hope.
The second is more tricky to distinguish even if you have a domain
knowledge, but not the real measurements with you. The GPU power
values is also a 'sensitive' knowledge to share. Open source guys can do
that (after measurements), but some vendor's engineers probably can't.