From: Pan Xinhui <xinhuix.pan@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, rjw@rjwysocki.net,
viresh.kumar@linaro.org, "mnipxh@163.com" <mnipxh@163.com>,
"yanmin_zhang@linux.intel.com" <yanmin_zhang@linux.intel.com>
Subject: Re: [PATCH V2] acpi-cpufreq: replace per_cpu with driver_data of policy
Date: Wed, 08 Jul 2015 20:28:28 +0800 [thread overview]
Message-ID: <559D176C.5000205@intel.com> (raw)
In-Reply-To: <20150707171126.GB12491@dtor-ws>
hi, Dmitry
thanks for your reply
On 2015年07月08日 01:11, Dmitry Torokhov wrote:
> Hi Pan,
>
> On Tue, Jul 07, 2015 at 08:43:26PM +0800, Pan Xinhui wrote:
>> @@ -364,19 +363,24 @@ static u32 get_cur_val(const struct cpumask *mask)
>>
>> static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
>> {
>> - struct acpi_cpufreq_data *data = per_cpu(acfreq_data, cpu);
>> + struct acpi_cpufreq_data *data;
>> + struct cpufreq_policy *policy;
>> unsigned int freq;
>> unsigned int cached_freq;
>>
>> pr_debug("get_cur_freq_on_cpu (%d)\n", cpu);
>>
>> - if (unlikely(data == NULL ||
>> - data->acpi_data == NULL || data->freq_table == NULL)) {
>> + policy = cpufreq_cpu_get(cpu);
>> + if (unlikely(!policy))
>> + return 0;
>> +
>> + data = policy->driver_data;
>> + cpufreq_cpu_put(policy);
>
> If we put policy here can we guarantee that memory pointed to by data
> stays valid? Shoudln't we issue cpufreq_cpu_put(policy) after we done
> assessing the pointer?
>
*driver_data* is used internal by acpi-cpufreq driver. So probably issuing
cpufreq_cpu_put(policy) after we get *driver_data* is OKay.
The worry you have is about the race. we set *driver_data* to NULL then
free it in ->exit callback while ->get callback is using it.
CPU A CPU B
->get ->exit
data = policy->driver_data;
if (!data ....)
policy->driver_data = NULL;
kfree(data);
access data ....
yes, it might happen in real world. As Viresh says, it is more like to be a core level work.
But this race exists in current codes, too. Maybe down_write policy->rwsem can avoid this race(need double check).
thanks for pointing out it. :)
thanks
xinhui
>> + if (unlikely(!data || !data->acpi_data || !data->freq_table))
>> return 0;
>> - }
>>
>> cached_freq = data->freq_table[data->acpi_data->state].frequency;
>> - freq = extract_freq(get_cur_val(cpumask_of(cpu)), data);
>> + freq = extract_freq(get_cur_val(cpumask_of(cpu), data), data);
>> if (freq != cached_freq) {
>> /*
>> * The dreaded BIOS frequency change behind our back.
>
> Thanks.
>
prev parent reply other threads:[~2015-07-08 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 12:43 [PATCH V2] acpi-cpufreq: replace per_cpu with driver_data of policy Pan Xinhui
2015-07-07 12:49 ` Pan Xinhui
2015-07-07 14:34 ` Viresh Kumar
2015-07-09 0:20 ` Rafael J. Wysocki
2015-07-09 1:28 ` Pan Xinhui
2015-07-10 1:16 ` Rafael J. Wysocki
2015-07-07 17:11 ` Dmitry Torokhov
2015-07-08 4:51 ` Viresh Kumar
2015-07-08 12:28 ` Pan Xinhui [this message]
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=559D176C.5000205@intel.com \
--to=xinhuix.pan@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mnipxh@163.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=yanmin_zhang@linux.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).