From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: 2.6.37 dom0 under Xen 4.1 clocksource not working
Date: Wed, 26 Jan 2011 17:18:03 -0800
Message-ID: <4D40C7CB.7000403@goop.org>
References: <4D2B206B.3010707@tycho.nsa.gov> <4D40407F.6000108@goop.org>
	<4D4047A0.6070803@tycho.nsa.gov>
	<alpine.DEB.2.00.1101261702240.7277@kaball-desktop>
	<20110126201226.GA22519@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110126201226.GA22519@dumpdata.com>
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: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>, xen-devel <xen-devel@lists.xensource.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 01/26/2011 12:12 PM, Konrad Rzeszutek Wilk wrote:
> Is this how 2.6.32 did it? Or was there no cpuidle driver in 2.6.32 so
> we never had tried this?

CPUIDLE is new.

>  With this being overwridden to HALT does that
> mean the hypervisor cycles through the Cx states? What about using
> MWAIT instead? How does this impact AMD platforms?

"halt" in this case is the safe_halt pvop, so it ends up going into the
appropriate hypercall.

    J