From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [RFC Patch] x86/hpet: Disable interrupts while running hpet interrupt handler.
Date: Tue, 06 Aug 2013 05:49:57 +0100 [thread overview]
Message-ID: <CE263F05.59FCC%keir.xen@gmail.com> (raw)
In-Reply-To: <1375735116-31466-1-git-send-email-andrew.cooper3@citrix.com>
On 05/08/2013 21:38, "Andrew Cooper" <andrew.cooper3@citrix.com> 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
next prev parent reply other threads:[~2013-08-06 4:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 20:38 [RFC Patch] x86/hpet: Disable interrupts while running hpet interrupt handler Andrew Cooper
2013-08-06 4:49 ` Keir Fraser [this message]
2013-08-06 8:01 ` Jan Beulich
2013-08-06 10:32 ` Andrew Cooper
2013-08-06 11:44 ` Jan Beulich
2013-08-06 13:23 ` Andrew Cooper
2013-08-06 13:57 ` Jan Beulich
2013-08-13 9:03 ` Hpet interrupt overflow Andrew Cooper
2013-08-13 9:22 ` Tim Deegan
2013-08-13 9:33 ` Andrew Cooper
2013-08-13 11:59 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CE263F05.59FCC%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.