From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755168Ab1BXVC1 (ORCPT ); Thu, 24 Feb 2011 16:02:27 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:35459 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753098Ab1BXVC0 (ORCPT ); Thu, 24 Feb 2011 16:02:26 -0500 Date: Thu, 24 Feb 2011 21:04:31 +0000 From: Alan Cox To: Thomas Gleixner Cc: Nicolas Pitre , Peter Zijlstra , Vincent Guittot , lkml , linux-hotplug@vger.kernel.org, Frederic Weisbecker , Steven Rostedt , amit.kucheria@linaro.org, Rusty Russell , Ingo Molnar Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events Message-ID: <20110224210431.7a6bba68@lxorguk.ukuu.org.uk> In-Reply-To: References: <1298573197.2428.457.camel@twins> <20110224201124.138311ba@lxorguk.ukuu.org.uk> <1298579452.5226.834.camel@laptop> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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. Alan