From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Rafael Wysocki <rjw@rjwysocki.net>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Avoid double addition/removal of sysfs links
Date: Wed, 22 Jul 2015 12:34:48 +0530 [thread overview]
Message-ID: <20150722070448.GC30970@linux> (raw)
In-Reply-To: <CAJZ5v0gHz5cEmX23uXESTmWbx5S+XsXMvxUp4ikTTpgdVy9N3w@mail.gmail.com>
On 21-07-15, 03:14, Rafael J. Wysocki wrote:
> That said, cpu_present_mask may only be updated after calling
> arch_unregister_cpu(), so checking it in cpufreq_remove_dev() doesn't
> really help.
No, it is indeed useful. This is a snippet from the latest code we
have:
cpumask_copy(&mask, policy->related_cpus);
cpumask_clear_cpu(cpu, &mask);
/*
* Free policy only if all policy->related_cpus are removed
* physically.
*/
if (cpumask_intersects(&mask, cpu_present_mask)) {
remove_cpu_dev_symlink(policy, cpu);
return 0;
}
cpufreq_policy_free(policy, true);
So what we are checking in the 'if' block is: "Is any CPU from
related_cpus, apart from the one getting removed now, present in the
system."
If not, then free the policy.
> It looks like using cpufreq_remove_dev() as the subsys ->remove_dev
> callback is a mistake as it cannot really tell the difference between
> that code path and the CPU offline one.
What do you mean by this? Doesn't the sif parameter confirms that its
called from subsys path ?
--
viresh
next prev parent reply other threads:[~2015-07-22 7:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 16:31 BUG: cpufreq on imx6solo warns Russell King - ARM Linux
2015-07-20 9:47 ` [PATCH] cpufreq: Avoid double addition/removal of sysfs links Viresh Kumar
2015-07-20 9:47 ` Viresh Kumar
2015-07-20 10:36 ` Russell King - ARM Linux
2015-07-21 0:47 ` Rafael J. Wysocki
2015-07-21 1:14 ` Rafael J. Wysocki
2015-07-22 7:04 ` Viresh Kumar [this message]
2015-07-21 10:43 ` Viresh Kumar
2015-07-22 6:57 ` Viresh Kumar
2015-07-21 23:15 ` Rafael J. Wysocki
2015-07-22 1:56 ` Rafael J. Wysocki
2015-07-22 3:00 ` Rafael J. Wysocki
2015-07-22 7:12 ` Viresh Kumar
2015-07-22 12:07 ` [PATCH V2] cpufreq: Fix double addition " Viresh Kumar
2015-07-22 12:07 ` Viresh Kumar
2015-07-22 12:44 ` Rafael J. Wysocki
2015-07-22 13:15 ` Russell King - ARM Linux
2015-07-22 16:42 ` Rafael J. Wysocki
2015-07-23 6:09 ` Viresh Kumar
2015-07-23 8:13 ` [PATCH 1/3] cpufreq: print error messages with dev_err() Viresh Kumar
2015-07-23 8:13 ` Viresh Kumar
2015-07-23 8:13 ` [PATCH 2/3] cpufreq: Create links for offline CPUs that got added earlier Viresh Kumar
2015-07-23 8:13 ` Viresh Kumar
2015-07-23 19:28 ` Rafael J. Wysocki
2015-07-23 8:13 ` [PATCH 3/3] cpufreq: use cpumask_test_and_clear_cpu() instead of separate routines Viresh Kumar
2015-07-23 8:13 ` Viresh Kumar
2015-07-23 17:22 ` [PATCH V2] cpufreq: Fix double addition of sysfs links Rafael J. Wysocki
2015-07-23 19:29 ` Rafael J. Wysocki
2015-07-23 5:54 ` Viresh Kumar
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=20150722070448.GC30970@linux \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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.