public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok Kataria <akataria@vmware.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>, Zachary Amsden <zach@vmware.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Alex Nixon <alex.nixon@citrix.com>, 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: Tue, 19 Aug 2008 12:22:12 -0700	[thread overview]
Message-ID: <1219173732.13032.43.camel@alok-dev1> (raw)
In-Reply-To: <86802c440808181836v7e1f12dbrf059c1be23f155dd@mail.gmail.com>

On Mon, 2008-08-18 at 18:36 -0700, Yinghai Lu wrote:
> On Mon, Aug 18, 2008 at 2:38 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > 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();
> >>  }
> >>
> 
> 
> Rusty,
> can you check tip/master with lguest?  wonder you need to do sth for lguest too.
> we are making 32 bit support per_cpu vector like 64 bit
> 
> also alok, can you check vmi etc...

Yes it crashes VMI too, i will get down to debug this maybe later in the
day. 
Thanks YH, for bringing this to my attention. 

Alok.



      reply	other threads:[~2008-08-19 19:22 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 ` [PATCH 1/2] Xen: Fix bug `do_IRQ: cannot handle IRQ -1 vector 0x6 cpu 1' Jeremy Fitzhardinge
2008-08-19  1:19   ` Ingo Molnar
2008-08-19  1:33     ` Yinghai Lu
2008-08-19  1:36   ` Yinghai Lu
2008-08-19 19:22     ` Alok Kataria [this message]

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=1219173732.13032.43.camel@alok-dev1 \
    --to=akataria@vmware.com \
    --cc=alex.nixon@citrix.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    --cc=zach@vmware.com \
    /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