From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>,
LKML <linux-kernel@vger.kernel.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest
Date: Tue, 25 Aug 2009 21:14:32 +0300 [thread overview]
Message-ID: <1251224072.13451.10.camel@penberg-laptop> (raw)
In-Reply-To: <4A94283C.6000405@goop.org>
On Tue, 2009-08-25 at 11:06 -0700, Jeremy Fitzhardinge wrote:
> On 08/25/09 09:52, Pekka Enberg wrote:
> > Hi Arnd,
> >
> > On Tue, 2009-08-25 at 18:49 +0200, Arnd Hannemann wrote:
> >
> >>> Thanks for doing the bisect! Can we also see your .config also?
> >>>
> >> Config for -rc7 is attached. My bisect configs were based on that
> >>
> > Thanks! While we wait for the Xen people, you can try the following
> > patch to see if we can narrow the bug down to trap_init().
> >
>
> I think there's a problem that the side-effect of this change is that
> interrupt initialization comes later, and so the dynamically allocated
> arrays are not set up when the first interrupt comes in.
Which interrupt initialization is that? We call trap_init() _earlier_
now.
> However, this particular change shouldn't have any effect on interrupts
> being enabled early, right?
Yeah, interrupt enabling should not be affected.
Pekka
next prev parent reply other threads:[~2009-08-25 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 15:48 [bisected] 2.6.31 regression: fails to boot as xen guest Arnd Hannemann
2009-08-25 16:29 ` Pekka Enberg
2009-08-25 16:49 ` Arnd Hannemann
2009-08-25 16:52 ` Pekka Enberg
2009-08-25 17:49 ` Arnd Hannemann
2009-08-25 18:03 ` Pekka Enberg
2009-08-25 18:08 ` Jeremy Fitzhardinge
2009-08-25 18:22 ` Arnd Hannemann
2009-08-25 18:25 ` Ingo Molnar
2009-08-25 18:30 ` Jeremy Fitzhardinge
2009-08-25 18:38 ` Arnd Hannemann
2009-08-25 18:43 ` Pekka Enberg
2009-08-25 19:31 ` Jeremy Fitzhardinge
2009-08-25 19:30 ` Jeremy Fitzhardinge
2009-08-25 18:58 ` Pekka Enberg
2009-08-25 19:07 ` Pekka Enberg
2009-08-25 19:13 ` Arnd Hannemann
2009-08-26 9:59 ` Benjamin Herrenschmidt
2009-08-25 18:06 ` Jeremy Fitzhardinge
2009-08-25 18:14 ` Pekka Enberg [this message]
2009-08-26 11:54 ` Pasi Kärkkäinen
2009-08-26 12:00 ` Pekka Enberg
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=1251224072.13451.10.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=Arnd.Hannemann@nets.rwth-aachen.de \
--cc=hannemann@nets.rwth-aachen.de \
--cc=hannes@cmpxchg.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xensource.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