Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp26438170rwd; Mon, 3 Jul 2023 09:39:03 -0700 (PDT) X-Google-Smtp-Source: APBJJlEuIa+XM3Vy8i1HXo8NlyxwBhMFCuZwmiOQmsB5Egrtj+wmGfxeICNN9kOqI3ZL10XY/PAI X-Received: by 2002:a17:902:bd8a:b0:1ae:8892:7d27 with SMTP id q10-20020a170902bd8a00b001ae88927d27mr10977685pls.42.1688402343173; Mon, 03 Jul 2023 09:39:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688402343; cv=none; d=google.com; s=arc-20160816; b=toRqVbibSaZllFisBdMty6V94GRPBPHSOWixjnbOvPDZuVHqcFX7MKr4UJIjkVdORO 6G8pyTxHGJsIjfswXRd+gXdRLKul949isDzSNDzZUdUpLI0Bu6U2cDXJ9+DKBEDM8WE0 e+OTTT5eBY7rp2FDwUrS7wds5JUC6qDmA0fjJovOvJE7yA50IFPArSmhafA7ogxsppQV dOX/owcwPm+7bQXkfDhBrtIBbLpwww7dorz4kELXc2sRDlg5gM56Uvo9nV2NrL+dCR03 CJyRMlkiqxUABSi2cTKznbV6+ELQesWmxCQY+BL3NMGminv806RJSzY1Ap9EsMe2jWyV bE7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=6MlxoltILSk6zrv/8bWHHheFJzIArbhwSrGExd1e4JI=; fh=Wo22gSJCRwTLyDzb41myy9Bl+2SFoGi1RZ4iP0fKd98=; b=Pk+tZtwXVnoikBBnA82xrnDYlRew8SE9QFk0ivUctZJzhjJewNLObWD95n6cy3in3L 5W2uNhpg4px+BlegFFwPbjDTgHntzMaTjzfXRID/B/Szwthvdecrl0tQCDSani1jf3ao TH1ddEZJrl0gl3CyFpZUFF8c+AhOzCUD3yYYHlCxHuiA0ljgbWiUi5Vf2twXnKlQs668 oVizOXuZv0SkOAp7EeQ5f9EH/HmRoXr8asOr9Lb/rdLNoTc5HqpysSc/Rm1wdRf6pwxJ Q3/RAUJ6E9f/d9O40Gjgbgb91rFTheeqh3A6PxPz/+3tbGYl6dkozex0MuSTuqIVTtos 04fg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j13-20020a170902c3cd00b001b86deba2fbsi7096525plj.605.2023.07.03.09.38.48; Mon, 03 Jul 2023 09:39:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230512AbjGCQJe (ORCPT + 99 others); Mon, 3 Jul 2023 12:09:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44882 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229885AbjGCQJd (ORCPT ); Mon, 3 Jul 2023 12:09:33 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 53A51138; Mon, 3 Jul 2023 09:09:32 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2F6172F4; Mon, 3 Jul 2023 09:10:14 -0700 (PDT) Received: from [10.57.27.93] (unknown [10.57.27.93]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E6DFF3F663; Mon, 3 Jul 2023 09:09:28 -0700 (PDT) Message-ID: Date: Mon, 3 Jul 2023 17:09:46 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH v2 14/17] Documentation: EM: Add a new section about the design Content-Language: en-US To: Dietmar Eggemann Cc: rui.zhang@intel.com, amit.kucheria@verdurent.com, amit.kachhap@gmail.com, daniel.lezcano@linaro.org, viresh.kumar@linaro.org, len.brown@intel.com, pavel@ucw.cz, Pierre.Gondois@arm.com, ionela.voinescu@arm.com, rostedt@goodmis.org, mhiramat@kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, rafael@kernel.org References: <20230512095743.3393563-1-lukasz.luba@arm.com> <20230512095743.3393563-15-lukasz.luba@arm.com> <0968c915-0344-b08f-7117-5b1ff6b126fd@arm.com> From: Lukasz Luba In-Reply-To: <0968c915-0344-b08f-7117-5b1ff6b126fd@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/30/23 11:33, Dietmar Eggemann wrote: > On 12/05/2023 11:57, Lukasz Luba wrote: >> Add a new section 'Design' which covers the information about Energy >> Model. It contains the design decisions, describes models and how they >> reflect the reality. Add description of the basic const. EM. Change the >> other section IDs. > > I would vote for coalescing the 4 doc patches into 1. OK, I can make that. I will be a big one patch, though. > >> >> Signed-off-by: Lukasz Luba >> --- >> Documentation/power/energy-model.rst | 36 +++++++++++++++++++++------- >> 1 file changed, 27 insertions(+), 9 deletions(-) >> >> diff --git a/Documentation/power/energy-model.rst b/Documentation/power/energy-model.rst >> index ef341be2882b..e97c7f18d8bd 100644 >> --- a/Documentation/power/energy-model.rst >> +++ b/Documentation/power/energy-model.rst >> @@ -72,16 +72,34 @@ required to have the same micro-architecture. CPUs in different performance >> domains can have different micro-architectures. >> >> >> -2. Core APIs >> +2. Design >> +----------------- >> + >> +2.1 Basic EM >> +^^^^^^^^^^^^ > > Can we make sure that people get the relation between 'basic' and > 'default' easier? > > It should be obvious that `pd->default_table->state` refers to this > `basic (const.) EM. Using the same identifier always helps in this > situation. OK, how about adding this: "The basic EM is built around const. power information for each performance state, which is accessible in: 'dev->em_pd->default_table->state'. This model can be derived based..." > >> + >> +The basic EM is built around const. power information for each performance >> +state. This model can be derived based on power measurements of the device >> +e.g. CPU while running some benchmark. The benchmark might be integer heavy >> +or floating point computation with a data set fitting into the CPU cache or >> +registers. Bare in mind that this model might not be covering all possible >> +workloads running on CPUs. Thus, please run a few different benchmarks and >> +verify with some real workloads your power model values. The power variation >> +due to the workload instruction mix and data set is not modeled. >> +Also static power which can change during runtime due to variation of SOC >> +temperature is not modeled in EM. >> + >> +