From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [RFC Patch] x86/hpet: Disable interrupts while running hpet interrupt handler. Date: Tue, 06 Aug 2013 05:49:57 +0100 Message-ID: References: <1375735116-31466-1-git-send-email-andrew.cooper3@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1375735116-31466-1-git-send-email-andrew.cooper3@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Xen-devel Cc: Tim Deegan , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 05/08/2013 21:38, "Andrew Cooper" wrote: > The hpet interrupt handler runs with interrupts enabled, due to this the > spin_unlock_irq() in: > > while ( desc->status & IRQ_PENDING ) > { > desc->status &= ~IRQ_PENDING; > spin_unlock_irq(&desc->lock); > tsc_in = tb_init_done ? get_cycles() : 0; > action->handler(irq, action->dev_id, regs); > TRACE_3D(TRC_HW_IRQ_HANDLED, irq, tsc_in, get_cycles()); > spin_lock_irq(&desc->lock); > } > > in do_IRQ(). But the handler sets IRQ_INPROGRESS before entering this loop, which should prevent reentry of the irq handler (hpet_interrupt_handler). So I don't see how the multiple reentering of hpet_interrupt_handler in the call trace is possible. -- Keir