From: Lingutla Chandrasekhar <clingutla@codeaurora.org>
To: will.deacon@arm.com, sudeep.holla@arm.com,
catalin.marinas@arm.com, dietmar.eggemann@arm.com
Cc: Lingutla Chandrasekhar <clingutla@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch_topology: Update user supplied capacity to possible cpus in cluster
Date: Thu, 28 Feb 2019 17:23:58 +0530 [thread overview]
Message-ID: <1551354838-29902-1-git-send-email-clingutla@codeaurora.org> (raw)
With commit '5bdd2b3f0f8 ("arm64: topology: add support to remove cpu
topology sibling masks")', when cpu hotplugged out, it resets the cpu
information in its sibling CPUs. If user changes capacity of any cpu,
then the new capacity applied to all online cpus in the cluster.
If any hot plugged out cpu in the same cluster comes back to online,
then that would have different/stale capacity value.
Fix it by applying user supplied capacity to all possible cpus in the
cluster.
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index edfcf8d..dadc5d8 100644
--- a/drivers/base/arch_topology.c
+++ b/drivers/base/arch_topology.c
@@ -61,6 +61,7 @@ static ssize_t cpu_capacity_store(struct device *dev,
int i;
unsigned long new_capacity;
ssize_t ret;
+ struct cpu_topology *icpu_topo, *this_topo = &cpu_topology[this_cpu];
if (!count)
return 0;
@@ -72,8 +73,15 @@ static ssize_t cpu_capacity_store(struct device *dev,
return -EINVAL;
mutex_lock(&cpu_scale_mutex);
- for_each_cpu(i, &cpu_topology[this_cpu].core_sibling)
+
+ for_each_possible_cpu(i) {
+ icpu_topo = &cpu_topology[i];
+
+ if (icpu_topo->package_id != this_topo->package_id)
+ continue;
topology_set_cpu_scale(i, new_capacity);
+ }
+
mutex_unlock(&cpu_scale_mutex);
schedule_work(&update_topology_flags_work);
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-28 11:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 11:53 Lingutla Chandrasekhar [this message]
2019-02-28 12:19 ` [PATCH] arch_topology: Update user supplied capacity to possible cpus in cluster Sudeep Holla
2019-02-28 14:38 ` Chandra Sekhar Lingutla
2019-02-28 15:25 ` Sudeep Holla
2019-03-02 13:30 ` Chandra Sekhar Lingutla
2019-03-04 18:21 ` Sudeep Holla
2019-03-05 9:23 ` Quentin Perret
2019-03-05 11:13 ` Sudeep Holla
2019-03-05 11:29 ` Quentin Perret
2019-03-05 11:36 ` Sudeep Holla
2019-03-05 15:53 ` Chandra Sekhar Lingutla
2019-03-05 16:12 ` Quentin Perret
2019-03-05 16:54 ` Sudeep Holla
2019-03-06 15:22 ` Morten Rasmussen
2019-03-06 15:27 ` [PATCH v1] arch_topology: Make cpu_capacity sysfs node as ready-only Lingutla Chandrasekhar
2019-03-06 15:27 ` Lingutla Chandrasekhar
2019-03-07 7:28 ` Juri Lelli
2019-03-07 7:28 ` Juri Lelli
2019-03-07 9:31 ` Quentin Perret
2019-03-07 9:31 ` Quentin Perret
2019-03-07 9:57 ` Juri Lelli
2019-03-07 9:57 ` Juri Lelli
2019-03-07 12:14 ` Quentin Perret
2019-03-07 12:14 ` Quentin Perret
2019-03-07 15:04 ` Sudeep Holla
2019-03-07 15:04 ` Sudeep Holla
2019-03-07 15:19 ` Sudeep Holla
2019-03-07 15:19 ` Sudeep Holla
2019-03-08 11:45 ` Dietmar Eggemann
2019-03-08 11:45 ` Dietmar Eggemann
2019-03-08 12:38 ` [PATCH v2] " Lingutla Chandrasekhar
2019-03-08 12:38 ` Lingutla Chandrasekhar
2019-03-27 10:56 ` Quentin Perret
2019-03-27 10:56 ` Quentin Perret
2019-03-06 9:48 ` [PATCH] arch_topology: Update user supplied capacity to possible cpus in cluster Dietmar Eggemann
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=1551354838-29902-1-git-send-email-clingutla@codeaurora.org \
--to=clingutla@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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.