From: Keir Fraser Subject: Re: Time goes backwards in dom0 in xen-unstable Date: Wed, 15 Apr 2009 10:18:53 +0100 Message-ID: References: <0A882F4D99BBF6449D58E61AAFD7EDD6103D46C5@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD6103D46C5@pdsmsx502.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , Dan Magenheimer , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org On 15/04/2009 08:51, "Tian, Kevin" wrote: > We revised our plan here, after realizing not-negligible effort to > enable RTC emulation. Instead we want to turn to an alternative > that hpet broadcast is always enabled once available (current > situation is to always give up if no MSI delivery support), and > then disable it on the fly (disable HPET interrupt and reduce > max_cstate to a level not requiring broadcast) once detecting > user trying to enable UIE/PIE/AIE on RTC. That way is far > simpler and makes cpuidle really available on most platforms > with HPET (true for most with VT support), in the meantime > not breaking occasional usage on RTC interrupt. > > Will you accept such patch which handles mostly about policy? :-) > We'll try to send it out today. It's got a better chance than RTC emulation. I'll certainly consider it. -- Keir