All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	rafael@kernel.org
Cc: lukasz.luba@arm.com, dietmar.eggemann@arm.com,
	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,
	mhiramat@kernel.org, qyousef@layalina.io, wvw@google.com,
	xuewen.yan94@gmail.com, Hongyan Xia <hongyan.xia2@arm.com>
Subject: [PATCH v8 04/23] PM: EM: Refactor em_pd_get_efficient_state() to be more flexible
Date: Thu,  8 Feb 2024 11:55:38 +0000	[thread overview]
Message-ID: <20240208115557.1273962-5-lukasz.luba@arm.com> (raw)
In-Reply-To: <20240208115557.1273962-1-lukasz.luba@arm.com>

The Energy Model (EM) is going to support runtime modification. There
are going to be 2 EM tables which store information. This patch aims
to prepare the code to be generic and use one of the tables. The function
will no longer get a pointer to 'struct em_perf_domain' (the EM) but
instead a pointer to 'struct em_perf_state' (which is one of the EM's
tables).

Prepare em_pd_get_efficient_state() for the upcoming changes and
make it possible to be re-used. Return an index for the best performance
state for a given EM table. The function arguments that are introduced
should allow to work on different performance state arrays. The caller of
em_pd_get_efficient_state() should be able to use the index either
on the default or the modifiable EM table.

Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Reviewed-by: Hongyan Xia <hongyan.xia2@arm.com>
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
---
 include/linux/energy_model.h | 30 +++++++++++++++++-------------
 1 file changed, 17 insertions(+), 13 deletions(-)

diff --git a/include/linux/energy_model.h b/include/linux/energy_model.h
index 88d91e087471..1dcd1645dde7 100644
--- a/include/linux/energy_model.h
+++ b/include/linux/energy_model.h
@@ -175,33 +175,35 @@ void em_dev_unregister_perf_domain(struct device *dev);
 
 /**
  * em_pd_get_efficient_state() - Get an efficient performance state from the EM
- * @pd   : Performance domain for which we want an efficient frequency
- * @freq : Frequency to map with the EM
+ * @table:		List of performance states, in ascending order
+ * @nr_perf_states:	Number of performance states
+ * @freq:		Frequency to map with the EM
+ * @pd_flags:		Performance Domain flags
  *
  * It is called from the scheduler code quite frequently and as a consequence
  * doesn't implement any check.
  *
- * Return: An efficient performance state, high enough to meet @freq
+ * Return: An efficient performance state id, high enough to meet @freq
  * requirement.
  */
-static inline
-struct em_perf_state *em_pd_get_efficient_state(struct em_perf_domain *pd,
-						unsigned long freq)
+static inline int
+em_pd_get_efficient_state(struct em_perf_state *table, int nr_perf_states,
+			  unsigned long freq, unsigned long pd_flags)
 {
 	struct em_perf_state *ps;
 	int i;
 
-	for (i = 0; i < pd->nr_perf_states; i++) {
-		ps = &pd->table[i];
+	for (i = 0; i < nr_perf_states; i++) {
+		ps = &table[i];
 		if (ps->frequency >= freq) {
-			if (pd->flags & EM_PERF_DOMAIN_SKIP_INEFFICIENCIES &&
+			if (pd_flags & EM_PERF_DOMAIN_SKIP_INEFFICIENCIES &&
 			    ps->flags & EM_PERF_STATE_INEFFICIENT)
 				continue;
-			break;
+			return i;
 		}
 	}
 
-	return ps;
+	return nr_perf_states - 1;
 }
 
 /**
@@ -226,7 +228,7 @@ static inline unsigned long em_cpu_energy(struct em_perf_domain *pd,
 {
 	unsigned long freq, ref_freq, scale_cpu;
 	struct em_perf_state *ps;
-	int cpu;
+	int cpu, i;
 
 	if (!sum_util)
 		return 0;
@@ -250,7 +252,9 @@ static inline unsigned long em_cpu_energy(struct em_perf_domain *pd,
 	 * Find the lowest performance state of the Energy Model above the
 	 * requested frequency.
 	 */
-	ps = em_pd_get_efficient_state(pd, freq);
+	i = em_pd_get_efficient_state(pd->table, pd->nr_perf_states, freq,
+				      pd->flags);
+	ps = &pd->table[i];
 
 	/*
 	 * The capacity of a CPU in the domain at the performance state (ps)
-- 
2.25.1


  parent reply	other threads:[~2024-02-08 11:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 11:55 [PATCH v8 00/23] Introduce runtime modifiable Energy Model Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 01/23] PM: EM: Add missing newline for the message log Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 02/23] PM: EM: Extend em_cpufreq_update_efficiencies() argument list Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 03/23] PM: EM: Find first CPU active while updating OPP efficiency Lukasz Luba
2024-02-08 11:55 ` Lukasz Luba [this message]
2024-02-08 11:55 ` [PATCH v8 05/23] PM: EM: Introduce em_compute_costs() Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 06/23] PM: EM: Check if the get_cost() callback is present in em_compute_costs() Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 07/23] PM: EM: Split the allocation and initialization of the EM table Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 08/23] PM: EM: Introduce runtime modifiable table Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 09/23] PM: EM: Use runtime modified EM for CPUs energy estimation in EAS Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 10/23] PM: EM: Add functions for memory allocations for new EM tables Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 11/23] PM: EM: Introduce em_dev_update_perf_domain() for EM updates Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 12/23] PM: EM: Add em_perf_state_from_pd() to get performance states table Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 13/23] PM: EM: Add performance field to struct em_perf_state and optimize Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 14/23] PM: EM: Support late CPUs booting and capacity adjustment Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 15/23] PM: EM: Optimize em_cpu_energy() and remove division Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 16/23] powercap/dtpm_cpu: Use new Energy Model interface to get table Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 17/23] powercap/dtpm_devfreq: " Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 18/23] drivers/thermal/cpufreq_cooling: Use new Energy Model interface Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 19/23] drivers/thermal/devfreq_cooling: " Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 20/23] PM: EM: Change debugfs configuration to use runtime EM table data Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 21/23] PM: EM: Remove old table Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 22/23] PM: EM: Add em_dev_compute_costs() Lukasz Luba
2024-02-08 11:55 ` [PATCH v8 23/23] Documentation: EM: Update with runtime modification design Lukasz Luba
2024-02-08 14:01 ` [PATCH v8 00/23] Introduce runtime modifiable Energy Model Rafael J. Wysocki
2024-02-08 15:00   ` Lukasz Luba

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=20240208115557.1273962-5-lukasz.luba@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=hongyan.xia2@arm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=wvw@google.com \
    --cc=xuewen.yan94@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.