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>,
"# 3.13.x" <stable@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject
Date: Mon, 02 Feb 2015 09:54:23 +0800 [thread overview]
Message-ID: <54CED8CF.9060407@oracle.com> (raw)
In-Reply-To: <CAKohpokstCHezi0-Vp=-WJn4Zrpnj0oELjw6jzkY_0976h3V8w@mail.gmail.com>
Viresh,
On 2015/1/30 12:14, Viresh Kumar wrote:
> On 30 January 2015 at 09:16, ethan zhao <ethan.zhao@oracle.com> wrote:
>> You mean the policy is shared by all CPUs, so PPC notification about one
> A policy may or maynot be shared by multiple CPUs. It all depends on your
> systems configuration. All CPUs which share clock line, share a policy.
>
> You can verify that from /sys/devices/system/cpu/cpu*/related_cpus. This
> gives the CPUs that share policy.
>
>> CPU should update all CPU's policy, right ? even the requested CPU is
>> shutting down.
> CPUs sharing policy have a single policy structure. And so policy would
> be updated for all CPUs that share the poilcy. Even if some cpu goes down,
> the policy might still be up and running.
Let' me check ACPI spec and BIOS to match your implementation.
About that patch you suggested, there is another question left pending:
Policy will be freed only when that's last CPU shutting down, how does it
happen when system booting ?
The description of the patch would be wrong (the Xen_bus call stack) --
Did the xen_bus shut down every CPU till the last during booting ?
Thanks,
Ethan
>
> --
> viresh
next prev parent reply other threads:[~2015-02-02 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 1:13 [PATCH] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject Viresh Kumar
2015-01-30 1:30 ` ethan zhao
2015-01-30 2:05 ` Viresh Kumar
2015-01-30 2:10 ` ethan zhao
2015-01-30 2:13 ` Viresh Kumar
2015-01-30 2:21 ` ethan zhao
2015-01-30 3:14 ` Viresh Kumar
2015-01-30 3:46 ` ethan zhao
2015-01-30 4:14 ` Viresh Kumar
2015-02-02 1:54 ` ethan zhao [this message]
2015-02-02 3:20 ` Viresh Kumar
2015-01-30 22:57 ` Rafael J. Wysocki
2015-01-30 22:55 ` santosh shilimkar
2015-01-31 0:31 ` 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=54CED8CF.9060407@oracle.com \
--to=ethan.zhao@oracle.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=santosh.shilimkar@oracle.com \
--cc=stable@vger.kernel.org \
--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 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.