This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 26 Jan 2011 17:18:03 -0800
Cc: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 26 Jan 2011 17:19:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110126201226.GA22519@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D2B206B.3010707@xxxxxxxxxxxxx> <4D40407F.6000108@xxxxxxxx> <4D4047A0.6070803@xxxxxxxxxxxxx> <alpine.DEB.2.00.1101261702240.7277@kaball-desktop> <20110126201226.GA22519@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7
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.


Xen-devel mailing list