From: Fabio Baltieri <fabio.baltieri@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
Rickard Andersson <rickard.andersson@stericsson.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] cpufreq: ondemand: handle SW coordinated CPUs
Date: Thu, 22 Nov 2012 18:02:37 +0100 [thread overview]
Message-ID: <20121122170237.GA16948@gmail.com> (raw)
In-Reply-To: <1708590.LLn32jdgxe@vostro.rjw.lan>
Hello Rafael,
thanks for the review! I only have one concern before sending a v4:
On Thu, Nov 22, 2012 at 01:10:15AM +0100, Rafael J. Wysocki wrote:
> > @@ -627,32 +659,41 @@ static void do_dbs_timer(struct work_struct *work)
> > delay -= jiffies % delay;
> > }
> > } else {
> > - __cpufreq_driver_target(dbs_info->cur_policy,
> > - dbs_info->freq_lo, CPUFREQ_RELATION_H);
> > + if (sample)
> > + __cpufreq_driver_target(dbs_info->cur_policy,
> > + dbs_info->freq_lo,
> > + CPUFREQ_RELATION_H);
> > delay = dbs_info->freq_lo_jiffies;
> > }
> > - schedule_delayed_work_on(cpu, &dbs_info->work, delay);
> > + schedule_delayed_work_on(smp_processor_id(), dw, delay);
>
> We're not supposed to be using smp_processor_id() any more.
> get_cpu()/put_cpu() should be used instead.
That's going to add preemption protection, do I need that? The function
is called from a kworker with the affinity set on a specific CPU, so it
should not migrate to a different one during execution.
I agree with you for all the other comments.
Thanks,
Fabio
--
Fabio Baltieri
next prev parent reply other threads:[~2012-11-22 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 12:06 [PATCH v3] cpufreq: ondemand: handle SW coordinated CPUs Fabio Baltieri
2012-11-20 12:06 ` Fabio Baltieri
2012-11-22 0:10 ` Rafael J. Wysocki
2012-11-22 17:02 ` Fabio Baltieri [this message]
2012-11-22 21:27 ` 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=20121122170237.GA16948@gmail.com \
--to=fabio.baltieri@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rickard.andersson@stericsson.com \
--cc=rjw@sisk.pl \
--cc=vincent.guittot@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.