[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.02.1104010006210.2797@x980>
Date: Fri, 01 Apr 2011 00:09:25 -0400 (EDT)
From: Len Brown <lenb@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Trinabh Gupta <trinabh@...ux.vnet.ibm.com>,
arjan@...ux.intel.com, Stephen Rothwell <sfr@...b.auug.org.au>,
suresh.b.siddha@...el.com, benh@...nel.crashing.org,
venki@...gle.com, ak@...ux.intel.com, linux-kernel@...r.kernel.org,
xen-devel@...ts.xensource.com
Subject: Re: cpuidle asymmetry (was Re: [RFC PATCH V4 5/5] cpuidle: cpuidle
driver for apm)
> > 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.
>
> 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?
they are smoking micro-amps:-)
S0i3 on cpu0 can be entered only after cpu1 is already off-line,
among other system hardware dependencies...
So it makes no sense to export S0i3 as a c-state on cpu1.
When cpu1 is online, the scheduler treats it as a normal SMP.
cheers,
-Len Brown, Intel Open Source Technology Center
--
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