From: Keir Fraser Subject: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options. Date: Fri, 16 Feb 2007 10:49:10 +0000 Message-ID: References: <45D56D5A.3000300@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45D56D5A.3000300@vmware.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: Dan Hecht , Jeremy Fitzhardinge Cc: xen-devel@lists.xensource.com, Ian Pratt , virtualization@lists.osdl.org, linux-kernel@vger.kernel.org, Chris Wright , Andi Kleen , Andrew Morton List-Id: xen-devel@lists.xenproject.org On 16/2/07 08:37, "Dan Hecht" wrote: > Hmm? I thought the periodic timer and one-shot timer both generate the > same VIRQ. So, how can you mask one without masking the other? > > The tickless idle works since the block hypercall disables the periodic > timer. But for dynticks (aka NO_HZ), you'll need to mask the periodic > timer (even for a running vcpu), while keeping the one-shot timer > unmasked. I don't think Xen provides an interface to do that. There's no interface for this right now, but we can easily add one in a backward compatible way. This also will not prevent a dyntick kernel from running on an older Xen -- the guest will then receive to many timer interrupts, but that should only be a performance concern fixable by upgrading the hypervisor component of the system. -- Keir