From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alex Nixon <alex.nixon@citrix.com>
Cc: Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Xen: Fix bug `do_IRQ: cannot handle IRQ -1 vector 0x6 cpu 1'
Date: Mon, 18 Aug 2008 14:38:05 -0700 [thread overview]
Message-ID: <48A9EBBD.5010509@goop.org> (raw)
In-Reply-To: <48A976E6.40906@citrix.com>
Alex Nixon wrote:
> From: Alex Nixon <alex.nixon@citrix.com>
> Date: Mon, 18 Aug 2008 12:56:48 +0100
> Subject: [PATCH] Xen: Fix bug `do_IRQ: cannot handle IRQ -1 vector 0x6 cpu 1'
>
> Following commit 9c3f2468d8339866d9ef6a25aae31a8909c6be0d, do_IRQ() looks up the IRQ number in the per-cpu variable vector_irq.
>
> This commit makes Xen initialise an identity vector_irq map for both X86_32 and X86_64.
>
Thanks Alex.
Ingo, please apply.
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Signed-off-by: Alex Nixon <alex.nixon@citrix.com>
> ---
> arch/x86/xen/irq.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/xen/irq.c b/arch/x86/xen/irq.c
> index 28b85ab..bb04260 100644
> --- a/arch/x86/xen/irq.c
> +++ b/arch/x86/xen/irq.c
> @@ -21,7 +21,6 @@ void xen_force_evtchn_callback(void)
>
> static void __init __xen_init_IRQ(void)
> {
> -#ifdef CONFIG_X86_64
> int i;
>
> /* Create identity vector->irq map */
> @@ -31,7 +30,6 @@ static void __init __xen_init_IRQ(void)
> for_each_possible_cpu(cpu)
> per_cpu(vector_irq, cpu)[i] = i;
> }
> -#endif /* CONFIG_X86_64 */
>
> xen_init_IRQ();
> }
>
next parent reply other threads:[~2008-08-18 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A976E6.40906@citrix.com>
2008-08-18 21:38 ` Jeremy Fitzhardinge [this message]
2008-08-19 1:19 ` [PATCH 1/2] Xen: Fix bug `do_IRQ: cannot handle IRQ -1 vector 0x6 cpu 1' Ingo Molnar
2008-08-19 1:33 ` Yinghai Lu
2008-08-19 1:36 ` Yinghai Lu
2008-08-19 19:22 ` Alok Kataria
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=48A9EBBD.5010509@goop.org \
--to=jeremy@goop.org \
--cc=alex.nixon@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox