From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Zijlstra <peterz@infradead.org>
Subject: Re: cpuidle asymmetry (was Re: [RFC PATCH V4 5/5]
 cpuidle: cpuidle driver for apm)
Date: Thu, 31 Mar 2011 15:18:56 +0200
Message-ID: <1301577536.4859.249.camel@twins>
References: <20110322123208.28725.30945.stgit@tringupt.in.ibm.com>
	<20110322123336.28725.29810.stgit@tringupt.in.ibm.com>
	<20110323121458.ec7cdaf9.sfr@canb.auug.org.au>
	<4D89CA7D.8080108@linux.vnet.ibm.com>
	<alpine.LFD.2.02.1103231623450.12911@x980>
	<4D8B550D.5000409@linux.vnet.ibm.com>
	<alpine.LFD.2.02.1103250321480.32565@x980>
	<20110325180156.GC19214@dirshya.in.ibm.com>
	<alpine.LFD.2.02.1103302203490.1920@x980>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <alpine.LFD.2.02.1103302203490.1920@x980>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Len Brown <lenb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, ak@linux.intel.com, suresh.b.siddha@intel.com, venki@google.com, benh@kernel.crashing.org, linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>, arjan@linux.intel.com, Trinabh Gupta <trinabh@linux.vnet.ibm.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2011-03-30 at 22:17 -0400, Len Brown wrote:
>=20
> Moorestown is already an example of an asymmetric system,
> since its deepest c-state is available on cpu0, but not on cpu1.
> So it needs different tables for each cpu.=20

wtf are these hardware guys smoking and how the heck are we supposed to
schedule on such a machine? Prefer to keep cpu1 busy while idling cpu0?