Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946240AbXBPTY6 (ORCPT ); Fri, 16 Feb 2007 14:24:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946239AbXBPTY6 (ORCPT ); Fri, 16 Feb 2007 14:24:58 -0500 Received: from gw.goop.org ([64.81.55.164]:46764 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946221AbXBPTY5 (ORCPT ); Fri, 16 Feb 2007 14:24:57 -0500 Message-ID: <45D60508.10000@goop.org> Date: Fri, 16 Feb 2007 11:24:56 -0800 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.9 (X11/20070212) MIME-Version: 1.0 To: Keir Fraser CC: xen-devel@lists.xensource.com, Andi Kleen , linux-kernel@vger.kernel.org, Ian Pratt , Chris Wright , virtualization@lists.osdl.org, Andrew Morton , Steven Hand , Christian Limpach Subject: Re: [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 876 Lines: 19 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/