From: Peter Zijlstra <peterz@infradead.org>
To: Chuansheng Liu <chuansheng.liu@intel.com>
Cc: luto@amacapital.net, daniel.lezcano@linaro.org,
rjw@rjwysocki.net, mingo@redhat.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, changcheng.liu@intel.com,
xiaoming.wang@intel.com, souvik.k.chakravarty@intel.com
Subject: Re: [PATCH 2/3] smp: Adding new function wake_up_all_cpus()
Date: Wed, 3 Sep 2014 11:52:51 +0200 [thread overview]
Message-ID: <20140903095251.GI4783@worktop.ger.corp.intel.com> (raw)
In-Reply-To: <1408351052-25075-2-git-send-email-chuansheng.liu@intel.com>
On Mon, Aug 18, 2014 at 04:37:31PM +0800, Chuansheng Liu wrote:
> Currently kick_all_cpus_sync() can break non-polling idle cpus
> thru IPI interrupts.
>
> But sometimes we need to break the polling idle cpus immediately
> to reselect the suitable c-state, also for non-idle cpus, we need
> to do nothing if we try to wake up them.
>
> Here adding one new function wake_up_all_cpus() to let all cpus out
> of idle based on function wake_up_if_idle().
wake_up_all_idle_cpus() ?
next prev parent reply other threads:[~2014-09-03 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 8:37 [PATCH 1/3] sched: Add new API wake_up_if_idle() to wake up the idle cpu Chuansheng Liu
2014-08-18 8:37 ` [PATCH 2/3] smp: Adding new function wake_up_all_cpus() Chuansheng Liu
2014-09-03 9:52 ` Peter Zijlstra [this message]
2014-08-18 8:37 ` [PATCH 3/3] cpuidle: Using the wake_up_all_cpus() to wake up all idle cpus Chuansheng Liu
2014-08-21 1:54 ` [PATCH 1/3] sched: Add new API wake_up_if_idle() to wake up the idle cpu Daniel Lezcano
2014-08-21 2:12 ` Liu, Chuansheng
2014-08-21 2:12 ` Liu, Chuansheng
2014-08-21 3:48 ` Daniel Lezcano
2014-08-21 21:21 ` Andy Lutomirski
2014-09-03 9:54 ` Peter Zijlstra
2014-09-03 9:58 ` Liu, Chuansheng
2014-09-03 9:51 ` Peter Zijlstra
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=20140903095251.GI4783@worktop.ger.corp.intel.com \
--to=peterz@infradead.org \
--cc=changcheng.liu@intel.com \
--cc=chuansheng.liu@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=souvik.k.chakravarty@intel.com \
--cc=xiaoming.wang@intel.com \
/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.