From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Vincent Guittot <vincent.guittot@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-hotplug@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
amit.kucheria@linaro.org, Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events
Date: Thu, 24 Feb 2011 20:47:23 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.1102242130360.2701@localhost6.localdomain6> (raw)
In-Reply-To: <1298579452.5226.834.camel@laptop>
On Thu, 24 Feb 2011, Peter Zijlstra wrote:
> On Thu, 2011-02-24 at 15:24 -0500, Nicolas Pitre wrote:
>
> > Most SMP ARM processors are going to use it soon. Powering down idle
> > cores provides substantial power saving.
>
> And why can't regular idle paths be used? CPU hotplug is a massively
> expensive operation.
To achieve the same result from idle, you need to exclude the core
from any unwanted wakeup. At the moment cpu unplug is the only way to
achieve that.
If you want to do the same from idle, then we need the isolation
features Frederic is working on for RT/HPC.
They allow us to isolate cores completely for totaly different
reasons, but it could be resused to provide full isolation of a core
in a very deep power state.
That would solve the problem w/o going through kstompmachine
Thanks,
tglx
next prev parent reply other threads:[~2011-02-24 20:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 17:33 [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events Vincent Guittot
2011-02-24 18:40 ` Thomas Gleixner
2011-02-28 13:36 ` Vincent Guittot
2011-03-02 10:08 ` Thomas Gleixner
2011-03-02 19:02 ` Vincent Guittot
2011-03-02 21:12 ` Thomas Gleixner
2011-02-24 18:46 ` Peter Zijlstra
2011-02-24 20:11 ` Alan Cox
2011-02-24 20:16 ` Thomas Gleixner
2011-02-24 20:24 ` Nicolas Pitre
2011-02-24 20:30 ` Peter Zijlstra
2011-02-24 20:40 ` Alan Cox
2011-02-24 20:40 ` Nicolas Pitre
2011-02-24 20:49 ` Peter Zijlstra
2011-02-24 20:49 ` Thomas Gleixner
2011-02-24 21:04 ` Alan Cox
2011-02-24 21:12 ` Thomas Gleixner
2011-02-24 21:17 ` Peter Zijlstra
2011-02-24 21:33 ` Thomas Gleixner
2011-02-24 20:47 ` Thomas Gleixner [this message]
2011-02-24 20:58 ` Peter Zijlstra
2011-02-24 21:03 ` Thomas Gleixner
2011-02-24 21:11 ` Paul E. McKenney
2011-02-24 20:27 ` 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=alpine.LFD.2.00.1102242130360.2701@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=amit.kucheria@linaro.org \
--cc=fweisbec@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nicolas.pitre@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox