From: Stephen Boyd <sboyd@codeaurora.org>
To: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
Cc: linux-pm@vger.kernel.org, Waldemar@codeaurora.org,
Rymarkiewicz@codeaurora.org, waldemar.rymarkiewicz@gmail.com,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH] PM / OPP: Don't check not plugged in CPUs to avoid error
Date: Thu, 13 Jul 2017 16:42:26 -0700 [thread overview]
Message-ID: <20170713234226.GE22780@codeaurora.org> (raw)
In-Reply-To: <20170713122201.30048-1-waldemarx.rymarkiewicz@intel.com>
On 07/13, Waldemar Rymarkiewicz wrote:
> On systems where not all possible CPUs are available for Linux call to
> dev_pm_opp_of_get_sharing_cpus() will fail as cannot find a cpu device
> for not present (not available) CPUs.
>
> Example (real use case):
> 2 physical MIPS cores, 4 VPE, cpu0/2 run Linux and cpu1/3 are not available
> for linux. cpufreq-dt driver + opp v2 fail to register opp_table due to the
> fact there is no struct device for cpu1 (cpu1 not available for Linux).
>
> Solve the problem by iterating over cpu_present_mask instead of
> cpu_possible_mask.
>
> Signed-off-by: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
> drivers/base/power/opp/of.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/power/opp/of.c b/drivers/base/power/opp/of.c
> index 57eec1c..389c924 100644
> --- a/drivers/base/power/opp/of.c
> +++ b/drivers/base/power/opp/of.c
> @@ -589,7 +589,7 @@ int dev_pm_opp_of_get_sharing_cpus(struct device *cpu_dev,
> if (!of_property_read_bool(np, "opp-shared"))
> goto put_cpu_node;
>
> - for_each_possible_cpu(cpu) {
> + for_each_present_cpu(cpu) {
> if (cpu == cpu_dev->id)
> continue;
>
Is there some way to iterate through all cpu nodes in DT without
using devices? I suppose some sort of loop on top of
of_get_cpu_node().
I worry that we may have some problem where we want to know about
all the CPUs that are sharing a particular OPP table but they
haven't been physically hotplugged yet. This also raises the
question about what the DT looks like before and after a CPU is
inserted into a system. If the non-present CPU nodes are in DT
all the time, then it may make sense for cpufreq-dt to intersect
the OPP sharing mask with the cpu_present_mask.
Probably nobody cares about knowing this difference though,
because we pretty much forward the result to cpufreq, so moving
to the present mask is good enough.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next parent reply other threads:[~2017-07-13 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170713122201.30048-1-waldemarx.rymarkiewicz@intel.com>
2017-07-13 23:42 ` Stephen Boyd [this message]
2017-07-17 7:12 ` [PATCH] PM / OPP: Don't check not plugged in CPUs to avoid error Viresh Kumar
2017-07-17 13:03 ` Waldemar Rymarkiewicz
2017-07-18 4:35 ` Viresh Kumar
2017-07-19 14:10 ` Waldemar Rymarkiewicz
2017-07-20 3:31 ` Viresh Kumar
2017-07-20 9:06 ` Waldemar Rymarkiewicz
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=20170713234226.GE22780@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=Rymarkiewicz@codeaurora.org \
--cc=Waldemar@codeaurora.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=vireshk@kernel.org \
--cc=waldemar.rymarkiewicz@gmail.com \
--cc=waldemarx.rymarkiewicz@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).