From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Gleixner <tglx@linutronix.de>
Date: Thu, 24 Feb 2011 20:16:01 +0000
Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events
Message-Id: <alpine.LFD.2.00.1102242115011.2701@localhost6.localdomain6>
List-Id: <linux-hotplug.vger.kernel.org>
References: <AANLkTinkctQ6Nek98JV7vaos34gD4Qn8nsuBzt=_Jj6T@mail.gmail.com> <1298573197.2428.457.camel@twins> <20110224201124.138311ba@lxorguk.ukuu.org.uk>
In-Reply-To: <20110224201124.138311ba@lxorguk.ukuu.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>, Vincent Guittot <vincent.guittot@linaro.org>, 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>

On Thu, 24 Feb 2011, Alan Cox wrote:

> > Anybody who is interested in the latency of cpu hotplug is deluding
> > himself, also cpu hotplug is _NOT_ a power management feature, so the
> > rest of your justification just disappeared as well.
> 
> Actually CPU hotplug is a power management feature on some devices where
> you need to shutdown one of the cores to enter low power modes.

Right.

> Remember we use it as part of the suspend paths and various processors
> nowdays drop into a suspend to RAM type state on CPU idling.

The suspend path is using it, but the cpu idle one is hardly using the
hotplug muck.

Thanks,

	tglx