From: Viresh Kumar <viresh.kumar@linaro.org>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
sboyd@codeaurora.org, prarit@redhat.com,
Srivatsa Bhat <srivatsa@mit.edu>
Subject: Re: [PATCH V7 2/6] cpufreq: Stop migrating sysfs files on hotplug
Date: Wed, 10 Jun 2015 07:49:12 +0530 [thread overview]
Message-ID: <20150610021912.GA26105@linux> (raw)
In-Reply-To: <557782C5.2030305@codeaurora.org>
On 09-06-15, 17:20, Saravana Kannan wrote:
> >[ Something similar attempted by Saravana earlier ]
> Full name and email would be nice.
Sure. @Rafael can you please hand edit this in case I am not required
to resend the patch ?
[ Something similar attempted by Saravana Kannan <skannan@codeaurora.org> earlier ]
> >+static void update_policy_cpu(struct cpufreq_policy *policy, unsigned int cpu)
> > {
> >- int ret;
> >-
> > if (WARN_ON(cpu == policy->cpu))
> Can you remind me again why this is a warning? Would we still need
> this check?
Its removed in a later commit. Its a warning because we are updating
policy->cpu here and that must have been done only if policy->cpu !=
cpu.
> >+ bool recover_policy = !sif;
> The policy is always going to be there, so calling it
> "recover_policy" is kinda confusing. But I can't suggest a better
> name now.
Not always. Its created as well sometimes :)
> >
> > pr_debug("adding CPU %u\n", cpu);
> >
> >+ /*
> >+ * Only possible if 'cpu' wasn't physically present earlier and we are
> >+ * here from subsys_interface add callback. A hotplug notifier will
> >+ * follow and we will handle it like logical CPU hotplug then. For now,
> >+ * just create the sysfs link.
> >+ */
> >+ if (cpu_is_offline(cpu)) {
> My changes were on an older code base, so things might have changed
> by now. But at this location, there was definitely a case where I
> had to check for "sif" before creating symlinks. I need to think a
cpu will be offline here only for sif==true.
> bit more to remember what that reason was and see if you have to do
> it too.
>
> I'll try to respond more later. But I just wanted to send out what I
> could when I have little time to review this.
Okay. Good to see you again.
--
viresh
next prev parent reply other threads:[~2015-06-10 2:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:55 [PATCH V7 0/6] cpufreq: Don't loose cpufreq history on CPU hotplug Viresh Kumar
2015-06-08 12:55 ` [PATCH V7 1/6] cpufreq: Don't allow updating inactive policies from sysfs Viresh Kumar
2015-06-08 23:19 ` Rafael J. Wysocki
2015-06-09 2:46 ` Viresh Kumar
2015-06-09 21:50 ` Saravana Kannan
2015-06-08 12:55 ` [PATCH V7 2/6] cpufreq: Stop migrating sysfs files on hotplug Viresh Kumar
2015-06-08 23:23 ` Rafael J. Wysocki
2015-06-09 2:50 ` Viresh Kumar
2015-06-10 0:20 ` Saravana Kannan
2015-06-10 2:19 ` Viresh Kumar [this message]
2015-06-10 23:29 ` Rafael J. Wysocki
2015-06-08 12:55 ` [PATCH V7 3/6] cpufreq: Initialize policy->kobj while allocating policy Viresh Kumar
2015-06-08 12:55 ` [PATCH V7 4/6] cpufreq: Call cpufreq_policy_put_kobj() from cpufreq_policy_free() Viresh Kumar
2015-06-08 12:55 ` [PATCH V7 5/6] cpufreq: Restart governor as soon as possible Viresh Kumar
2015-06-08 23:27 ` Rafael J. Wysocki
2015-06-09 3:09 ` Viresh Kumar
2015-06-08 12:55 ` [PATCH V7 6/6] cpufreq: Remove cpufreq_update_policy() Viresh Kumar
2015-06-08 23:17 ` [PATCH V7 0/6] cpufreq: Don't loose cpufreq history on CPU hotplug 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=20150610021912.GA26105@linux \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=skannan@codeaurora.org \
--cc=srivatsa@mit.edu \
/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).