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 12:06:02 +0800 [thread overview]
Message-ID: <54CEF7AA.80401@oracle.com> (raw)
In-Reply-To: <CAKohpom589bFL4-eyR1=qrc6uoRtjck_z_SBHS3XU8dJSc4yFg@mail.gmail.com>
On 2015/2/2 11:59, Viresh Kumar wrote:
> On 2 February 2015 at 09:26, ethan zhao <ethan.zhao@oracle.com> wrote:
>> How to prevent the policy to be freed between
>>
>> cpufreq_cpu_get() and cpufreq_cpu_put() ?
> kobject_get() increases the reference count of a policy and the policy
> will only be freed when this is zero. And it will only be zero once all
> cpufreq_cpu_get() are matched with corresponding cpufreq_cpu_put().
Is that an idea it supposed to be or fact ?
if (!cpufreq_suspended)
cpufreq_policy_free(policy);
static void cpufreq_policy_free(struct cpufreq_policy *policy)
{
free_cpumask_var(policy->related_cpus);
free_cpumask_var(policy->cpus);
kfree(policy);
}
It seems you just think about it ideally in mind.
Thanks,
Ethan
>
>> You are maxing up the water with sand ?
> :)
next prev parent reply other threads:[~2015-02-02 4:06 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 [this message]
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
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=54CEF7AA.80401@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).