From: ethan zhao <ethan.zhao@oracle.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
santosh shilimkar <santosh.shilimkar@oracle.com>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH Resend] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject
Date: Mon, 02 Feb 2015 23:04:41 +0800 [thread overview]
Message-ID: <54CF9209.1050403@oracle.com> (raw)
In-Reply-To: <CAKohpomYpEAeQeaB7HVT0cBT5H_P8QQ-e+FQ5OqUoOvfz2ZnOQ@mail.gmail.com>
On 2015/2/2 12:54, Viresh Kumar wrote:
> On 2 February 2015 at 10:15, ethan zhao <ethan.zhao@oracle.com> wrote:
>> On 2015/2/2 12:26, Viresh Kumar wrote:
>> But there is no checking against refcount in or before
>>
>> cpufreq_policy_free(), that is one issue I mentioned.
> As I said earlier, the completion will only fire once the refcount
> is zero. And so there is no need of any check here.
>
>>> That routines doesn't have any tricks and simply frees the policy.
>>> Because, before calling cpufreq_policy_put_kobj(), we have set
>>> the per-cpu variable to NULL, nobody else will get the policy
>> It is possible cpufreq_cpu_get() within the PPC thread was called just
>> before __cpufreq_remove_dev_finish() is to be called in another thread,
>> so you set the per_cpu(cpufreq_cpu_data, cpu) to NULL will not prevent
>> the actions between cpufreq_cpu_get and cpufreq_cpu_put().
>>
>> And then the freeing happens in __cpufreq_remove_dev_finish().
> It will.. You aren't looking closely enough. If cpufreq_cpu_get() is called just
> before remove-dev, then cpufreq_cpu_get() will take:
>
> read_lock_irqsave(&cpufreq_driver_lock, flags);
>
> And it will do:
>
> read_unlock_irqrestore(&cpufreq_driver_lock, flags);
>
> only after increasing the refcount with kobject_get().
>
> While on the other side __cpufreq_remove_dev_finish() will do this:
>
> write_lock_irqsave(&cpufreq_driver_lock, flags);
> policy = per_cpu(cpufreq_cpu_data, cpu);
> per_cpu(cpufreq_cpu_data, cpu) = NULL;
> write_unlock_irqrestore(&cpufreq_driver_lock, flags);
>
> So, it will wait for the read_lock in cpufreq_cpu_get() to finish before
> setting per-cpu variable to NULL. And so, after kobject_put() in
> cpufreq_policy_put_kobj(), we will wait for the completion to fire
Closely enough this time, understood, thanks for your explanation.
Ethan
> and that will only happen once a corresponding cpufreq_cpu_put()
> is issued.
next prev parent reply other threads:[~2015-02-02 15:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 0:32 [PATCH Resend] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject Viresh Kumar
2015-01-31 2:14 ` Viresh Kumar
2015-02-02 3:20 ` ethan zhao
2015-02-02 3:24 ` Viresh Kumar
2015-02-02 3:38 ` ethan zhao
2015-02-02 3:43 ` Viresh Kumar
2015-02-02 3:56 ` ethan zhao
2015-02-02 3:59 ` Viresh Kumar
2015-02-02 4:06 ` ethan zhao
2015-02-02 4:09 ` Viresh Kumar
2015-02-02 4:16 ` ethan zhao
2015-02-02 4:26 ` Viresh Kumar
2015-02-02 4:45 ` ethan zhao
2015-02-02 4:54 ` Viresh Kumar
2015-02-02 15:04 ` ethan zhao [this message]
2015-02-25 3:24 ` Ethan Zhao
2015-02-25 4:35 ` viresh kumar
2015-02-25 5:47 ` Ethan Zhao
2015-02-25 16:31 ` santosh shilimkar
2015-03-09 1:34 ` Ethan Zhao
2015-03-09 4:06 ` Viresh Kumar
2015-03-09 4:14 ` ethan zhao
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=54CF9209.1050403@oracle.com \
--to=ethan.zhao@oracle.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=santosh.shilimkar@oracle.com \
--cc=viresh.kumar@linaro.org \
/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).