From: Ingo Molnar <mingo@elte.hu>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 12:53:32 +0200 [thread overview]
Message-ID: <20080526105332.GA484@elte.hu> (raw)
In-Reply-To: <483A9050.5000206@jp.fujitsu.com>
* Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> wrote:
> Although I have not considered how to implement proper fix deeply, I
> don't think it's so simple. For example, current pciehp is doing like
> this:
>
> (1) some initialization
> (2) request_irq()
> (3) issue command
> (4) initialize slot data structure
>
> Maybe we want to do (2) after (4) to fix the problem. But if we simply
> move (2) after (4), we cannot detect the command completion event at
> (3) and it will cause command timeout.
>
> It's just an example, and there might be other things like this. This
> example might be fixed simply, but all my worry is that fixing this
> quickly might cause another regressions. This is why I think Ingo's
> approach is better in a short term.
>
> And another reason is I'm very nervous because I already caused many
> problems in pciehp since 2.6.26-rcX... :(
no need to feel bad about it - i dont think what i reported is a serious
problem in any fashion - it's a very narrow race as long as DEBUG_SHIRQ
is off that very likely wont trigger in practice. We can do a minimal
fix in v2.6.26 and something more structural in v2.6.27.
Ingo
next prev parent reply other threads:[~2008-05-26 10:54 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
2008-05-26 10:26 ` Kenji Kaneshige
2008-05-26 10:53 ` Ingo Molnar [this message]
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=20080526105332.GA484@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.