public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	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 19:26:24 +0900	[thread overview]
Message-ID: <483A9050.5000206@jp.fujitsu.com> (raw)
In-Reply-To: <20080526015232.5faac5bb.akpm@linux-foundation.org>

Andrew Morton 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?
> 

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... :(

Thanks,
Kenji Kaneshige





  parent reply	other threads:[~2008-05-26 10:28 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 [this message]
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=483A9050.5000206@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=drzeus-list@drzeus.cx \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox