From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
drzeus-list@drzeus.cx
Subject: Re: [patch, -git] pcie hotplug bootup crash fix
Date: Mon, 26 May 2008 10:58:24 +0200 [thread overview]
Message-ID: <20080526085824.GA13529@elte.hu> (raw)
In-Reply-To: <20080526015232.5faac5bb.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 26 May 2008 10:47:09 +0200 Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> wrote:
> >
> > > I updated Ingo's patch. If it's ok, I'll send it to Jess Barnes with
> > > some other patches for the other pciehp regression problems.
> >
> > looks good to me, thanks Kenji.
> >
>
> It's a bit sad to add a large workaround like this. I'm surprised
> that fixing it properly is considered unviable for 2.6.26. Normally
> these fixes are pretty simple - just request the IRQ a bit later?
hm, will that solve the problem? These irqs can be shared and there can
be multiple of them, so making the handlers robust against
half-constructed global state seems inevitable (the other option would
be extra locking). But i've only looked briefly ...
Ingo
next prev parent reply other threads:[~2008-05-26 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 16:58 [patch, -git] pcie hotplug bootup crash fix Ingo Molnar
2008-05-24 17:40 ` Andrew Morton
2008-05-26 8:35 ` Kenji Kaneshige
2008-05-26 8:47 ` Ingo Molnar
2008-05-26 8:52 ` Andrew Morton
2008-05-26 8:58 ` Ingo Molnar [this message]
2008-05-26 10:26 ` Kenji Kaneshige
2008-05-26 10:53 ` Ingo Molnar
2008-05-26 16:20 ` Jesse Barnes
2008-05-27 22:45 ` Kristen Carlson Accardi
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=20080526085824.GA13529@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=drzeus-list@drzeus.cx \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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.