[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1102242206560.2701@localhost6.localdomain6>
Date: Thu, 24 Feb 2011 22:12:32 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
cc: Nicolas Pitre <nicolas.pitre@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
lkml <linux-kernel@...r.kernel.org>,
linux-hotplug@...r.kernel.org,
Frederic Weisbecker <fweisbec@...il.com>,
Steven Rostedt <rostedt@...dmis.org>, amit.kucheria@...aro.org,
Rusty Russell <rusty@...tcorp.com.au>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events
On Thu, 24 Feb 2011, Alan Cox wrote:
> > That's the equivalent of physical hotplug, but we still have all the
> > memory state around, so it is possible from idle, when we have the
>
> All sorts of other state goes walking as well though - on die device
> state for example like the GPU context may well also evaporate or
> disappear except for the minimum needed for scanout.
>
> It's not just about the CPU its a system (albeit a SoC in most cases)
> going to sleep lock stock and barrel except for IRQ notifications, and in
> some cases things like offloaded audio playback.
I guess we are talking about different things.
If you take down one core of a package then it does not take down the
whole SoC and does not take down devices either. Device take down is
or should be handled by explicit clock and power gating.
If you take down the whole SoC, then it's full S2RAM or some
equivilant thing. That's a different story and propably requires the
whole hotplug muck.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists