From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options. Date: Fri, 16 Feb 2007 11:24:56 -0800 Message-ID: <45D60508.10000@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, virtualization@lists.osdl.org, Steven Hand , linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen , Andrew Morton , Ian Pratt , Christian Limpach List-Id: virtualization@lists.linuxfoundation.org Keir Fraser wrote: > We can extend the Xen timer interface quite easily and get rid of this one > too. In fact it doesn't *much* matter if the CONFIG_HZ differs from the Xen > ticker rate -- we modified the Linux timer ISR to handle timer interrupts at > arbitrary times already. The only drawback is that jiffies updates in burts > if CONFIG_HZ is higher than the actual tick rate, and this can affect some > calibration constants and cause Linux to print out some weird values at > start-of-day. > I was wondering what would happen if we tried that. I guess its equivalent to having stolen time between each Xen tick. J