From: Viresh Kumar <viresh.kumar@linaro.org>
To: Guru Prasad <gurupras@buffalo.edu>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Re: Changing CPU frequency in atomic (schedule / scheduler_tick)
Date: Tue, 18 Aug 2015 19:36:01 +0530 [thread overview]
Message-ID: <20150818140601.GE31148@linux> (raw)
In-Reply-To: <CAMefCkDiudnfS2rWWf2Bfev3mOdWiSifO195amsAyLJ7Y4bQqQ@mail.gmail.com>
On 18-08-15, 09:05, Guru Prasad wrote:
> I don't think this will allow me to have a per-process frequency setting.
>
> The problem I see with this approach is that, the scheduled work is
> run in its own context, which means there will be a context switch.
> When this happens, another instance of the work will be scheduled
> (from schedule() ). I imagine I would need a conditional call to
> schedule_work(). Something like:
> if(!is_kthread(next))
> schedule_work(...);
There is work in progress on what you are looking for, look for this
thread:
http://marc.info/?l=linux-kernel&m=143077749912612
--
viresh
prev parent reply other threads:[~2015-08-18 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 3:46 Changing CPU frequency in atomic (schedule / scheduler_tick) Guru Prasad
2015-08-18 10:27 ` Viresh Kumar
2015-08-18 13:05 ` Guru Prasad
2015-08-18 13:57 ` Guru Prasad
2015-12-10 10:39 ` Punit Agrawal
2015-08-18 14:06 ` Viresh Kumar [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=20150818140601.GE31148@linux \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=gurupras@buffalo.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).