From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Keir (Xen.org)" <keir@xen.org>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Revert "irq: Add extra debugging to help track down why an assertion is failing"
Date: Wed, 5 Jun 2013 10:19:37 +0100 [thread overview]
Message-ID: <51AF02A9.2090408@citrix.com> (raw)
In-Reply-To: <51AF1D7302000078000DB5E0@nat28.tlf.novell.com>
On 05/06/13 10:13, Jan Beulich wrote:
> This reverts commits 2ae8b9173fb2388af6514c730d620ed5f450bc34 and
> 98e10364bde098e12104caa4f566b17d05f8b791.
>
> This was never reported to be hit, and we assume to have taken care of
> the problem by excluding legacy IRQs from the IRQ move cleanup logic.
>
> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> --- a/xen/arch/x86/irq.c
> +++ b/xen/arch/x86/irq.c
> @@ -624,8 +624,6 @@ void move_native_irq(struct irq_desc *de
> desc->handler->enable(desc);
> }
>
> -static void dump_irqs(unsigned char key);
> -
> void irq_move_cleanup_interrupt(struct cpu_user_regs *regs)
> {
> unsigned vector, me;
> @@ -687,19 +685,7 @@ void irq_move_cleanup_interrupt(struct c
>
> if ( desc->arch.used_vectors )
> {
> - if ( unlikely(!test_bit(vector, desc->arch.used_vectors)) )
> - {
> - spin_unlock(&desc->lock);
> - bitmap_scnlistprintf(keyhandler_scratch,
> - sizeof(keyhandler_scratch),
> - desc->arch.used_vectors->_bits,
> - NR_VECTORS);
> - printk("*** IRQ BUG found ***\n"
> - "CPU%d -Testing vector %d from bitmap %s\n",
> - me, vector, keyhandler_scratch);
> - dump_irqs('i');
> - BUG();
> - }
> + ASSERT(test_bit(vector, desc->arch.used_vectors));
> clear_bit(vector, desc->arch.used_vectors);
> }
> }
>
>
>
next prev parent reply other threads:[~2013-06-05 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 9:13 [PATCH] Revert "irq: Add extra debugging to help track down why an assertion is failing" Jan Beulich
2013-06-05 9:19 ` Andrew Cooper [this message]
2013-06-05 10:37 ` George Dunlap
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=51AF02A9.2090408@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@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.