From: Guenter Roeck <linux@roeck-us.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Yuanquan.Chen@freescale.com, linuxppc-dev@lists.ozlabs.org,
Gavin Shan <shangw@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/pci: Avoid overriding MSI interrupt
Date: Sat, 29 Jun 2013 18:29:20 -0700 [thread overview]
Message-ID: <20130630012920.GA2673@roeck-us.net> (raw)
In-Reply-To: <1372547360.18612.76.camel@pasglop>
On Sun, Jun 30, 2013 at 09:09:20AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2013-06-28 at 21:10 +0800, Gavin Shan wrote:
> > The issue was introduced by commit 37f02195 ("powerpc/pci: fix
> > PCI-e devices rescan issue on powerpc platform"). The field
> > (struct pci_dev::irq) is reused by PCI core to trace the base
> > MSI interrupt number if the MSI stuff is enabled on the corresponding
> > device. When running to pcibios_setup_device(), we possibly still
> > have enabled MSI interrupt on the device. That means "pci_dev->irq"
> > still have the base MSI interrupt number and it will be overwritten
> > if we're going fix "pci_dev->irq" again by pci_read_irq_line().
> > Eventually, when we enable the device, it runs to kernel crash caused
> > by fetching the the MSI interrupt descriptor (struct msi_desc) from
> > non-MSI interrupt and using the NULL descriptor.
>
> So finally I decided instead to apply Guenter patch
>
> [PATCH v2] powerpc/pci: Improve device hotplug initialization
>
> Which fixes the underlying problem instead.
>
Guess I am not hitting above bug because I have my own patch applied ;).
Thanks a lot!
Guenter
next prev parent reply other threads:[~2013-06-30 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 13:10 [PATCH] powerpc/pci: Avoid overriding MSI interrupt Gavin Shan
2013-06-29 7:20 ` Benjamin Herrenschmidt
2013-06-29 23:09 ` Benjamin Herrenschmidt
2013-06-30 1:29 ` Guenter Roeck [this message]
2013-06-30 1:51 ` Gavin Shan
2013-06-30 4:06 ` Benjamin Herrenschmidt
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=20130630012920.GA2673@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Yuanquan.Chen@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shangw@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).