From: Viresh Kumar <viresh.kumar@linaro.org>
To: Yuantian Tang <Yuantian.Tang@freescale.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Hongbo Zhang <hongbo.zhang@freescale.com>,
"LeoLi@freescale.com" <LeoLi@freescale.com>
Subject: Re: [PATCH 2/2] cpufreq: ppc-corenet: remove per-cpu variable 'cpu_mask'
Date: Tue, 2 Sep 2014 12:19:26 +0530 [thread overview]
Message-ID: <CAKohpokQo=Jqgj2CzTH41WbD6F1GpdhksWdg0dm8WLN_CT5KkA@mail.gmail.com> (raw)
In-Reply-To: <6a145a322bd64e14a2d94e8c40151bbe@BY2PR03MB570.namprd03.prod.outlook.com>
On 2 September 2014 12:16, Yuantian Tang <Yuantian.Tang@freescale.com> wrote:
> Hello Viresh:
>
> Probably it is not right considering the CPU cluster and CPU hotplug case.
So in case of hotplug the worst that can happen is policy->cpu gets updated.
But because we are all concerned about cpu_data here, which is stored in
per-cpu variables and is updated for all online CPUs, it should work.
I would like to see how that fails :)
next prev parent reply other threads:[~2014-09-02 6:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 3:41 [PATCH 1/2] cpufreq: ppc-corenet: remove duplicate update of cpu_data Viresh Kumar
2014-09-02 3:41 ` [PATCH 2/2] cpufreq: ppc-corenet: remove per-cpu variable 'cpu_mask' Viresh Kumar
2014-09-02 6:46 ` Yuantian Tang
2014-09-02 6:49 ` Viresh Kumar [this message]
2014-09-02 7:02 ` Yuantian Tang
2014-09-02 7:09 ` Viresh Kumar
2014-09-02 8:08 ` Yuantian Tang
2014-09-03 8:02 ` Yuantian Tang
2014-09-03 9:50 ` Viresh Kumar
2014-09-04 2:51 ` Yuantian Tang
2014-09-04 3:38 ` Viresh Kumar
2014-09-04 4:33 ` Yuantian Tang
2014-09-04 4:37 ` Viresh Kumar
2014-09-05 9:35 ` Yuantian Tang
2014-09-05 9:40 ` Viresh Kumar
2014-09-02 6:38 ` [PATCH 1/2] cpufreq: ppc-corenet: remove duplicate update of cpu_data Yuantian Tang
2014-09-02 6:47 ` Viresh Kumar
2014-09-10 4:32 ` Viresh Kumar
2014-09-10 5:30 ` Yuantian Tang
2014-09-10 5:39 ` Viresh Kumar
2014-09-10 6:19 ` Yuantian Tang
2014-09-10 6:20 ` Yuantian Tang
2014-09-24 23:45 ` Rafael J. Wysocki
2014-09-29 9:05 ` Viresh Kumar
2014-09-29 23:41 ` Rafael J. Wysocki
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='CAKohpokQo=Jqgj2CzTH41WbD6F1GpdhksWdg0dm8WLN_CT5KkA@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=LeoLi@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=hongbo.zhang@freescale.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.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.