[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210615050949.10071-1-psampat@linux.ibm.com>
Date: Tue, 15 Jun 2021 10:39:49 +0530
From: "Pratik R. Sampat" <psampat@...ux.ibm.com>
To: mpe@...erman.id.au, rjw@...ysocki.net, linux-pm@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
psampat@...ux.ibm.com, pratik.r.sampat@...il.com
Subject: [PATCH] cpufreq:powernv: Fix init_chip_info initialization in numa=off
In the numa=off kernel command-line configuration init_chip_info() loops
around the number of chips and attempts to copy the cpumask of that node
which is NULL for all iterations after the first chip.
Hence adding a check to bail out after the first initialization if there
is only one node.
Fixes: 053819e0bf84 ("cpufreq: powernv: Handle throttling due to Pmax capping at chip level")
Signed-off-by: Pratik R. Sampat <psampat@...ux.ibm.com>
Reported-by: Shirisha Ganta <shirishaganta1@....com>
---
drivers/cpufreq/powernv-cpufreq.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
index e439b43c19eb..663f9c4b5e3a 100644
--- a/drivers/cpufreq/powernv-cpufreq.c
+++ b/drivers/cpufreq/powernv-cpufreq.c
@@ -1078,6 +1078,8 @@ static int init_chip_info(void)
INIT_WORK(&chips[i].throttle, powernv_cpufreq_work_fn);
for_each_cpu(cpu, &chips[i].mask)
per_cpu(chip_info, cpu) = &chips[i];
+ if (num_possible_nodes() == 1)
+ break;
}
free_and_return:
--
2.30.2
Powered by blists - more mailing lists