Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-09 Thread Bjorn Helgaas
On Tue, Dec 08, 2015 at 10:05:56AM +0100, Sebastian Andrzej Siewior wrote: > * Bjorn Helgaas | 2015-12-04 12:46:19 [-0600]: > > >The backtrace might be OK (maybe slightly overkill), but all the > >stack addresses are certainly irrelevant and distracting. We only > >need enough to recognize the

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-09 Thread Grygorii Strashko
On 12/09/2015 05:24 PM, Bjorn Helgaas wrote: On Tue, Dec 08, 2015 at 10:05:56AM +0100, Sebastian Andrzej Siewior wrote: * Bjorn Helgaas | 2015-12-04 12:46:19 [-0600]: The backtrace might be OK (maybe slightly overkill), but all the stack addresses are certainly irrelevant and distracting. We

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-08 Thread Lucas Stach
Hi Bjorn, Am Montag, den 07.12.2015, 21:33 -0600 schrieb Bjorn Helgaas: > [+cc Jingoo (exynos), Richard, Lucas (imx6), Pratyush (spear13xx)] > > On Fri, Dec 04, 2015 at 11:22:50PM +0200, Grygorii Strashko wrote: > > On 12/04/2015 08:46 PM, Bjorn Helgaas wrote: > > > Hi Grygorii, [...] > > >>

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-08 Thread Sebastian Andrzej Siewior
* Bjorn Helgaas | 2015-12-04 12:46:19 [-0600]: >The backtrace might be OK (maybe slightly overkill), but all the >stack addresses are certainly irrelevant and distracting. We only >need enough to recognize the problem. I don't think the modules list >is relevant either. I would shorten it to

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-08 Thread Pratyush Anand
On Tue, Dec 8, 2015 at 2:53 PM, Lucas Stach wrote: > Hi Bjorn, > > Am Montag, den 07.12.2015, 21:33 -0600 schrieb Bjorn Helgaas: >> [+cc Jingoo (exynos), Richard, Lucas (imx6), Pratyush (spear13xx)] >> >> On Fri, Dec 04, 2015 at 11:22:50PM +0200, Grygorii Strashko wrote:

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-07 Thread Bjorn Helgaas
[+cc Jingoo (exynos), Richard, Lucas (imx6), Pratyush (spear13xx)] On Fri, Dec 04, 2015 at 11:22:50PM +0200, Grygorii Strashko wrote: > On 12/04/2015 08:46 PM, Bjorn Helgaas wrote: > > Hi Grygorii, > > > > On Fri, Nov 20, 2015 at 03:59:26PM +0200, Grygorii Strashko wrote: > >> On -RT, TI DRA7

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-04 Thread Grygorii Strashko
On 12/04/2015 08:46 PM, Bjorn Helgaas wrote: > Hi Grygorii, > > On Fri, Nov 20, 2015 at 03:59:26PM +0200, Grygorii Strashko wrote: >> On -RT, TI DRA7 PCIe driver always produces below backtrace when the >> first PCI interrupt is triggered: >> >> [ cut here ] >> WARNING:

Re: [PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-12-04 Thread Bjorn Helgaas
Hi Grygorii, On Fri, Nov 20, 2015 at 03:59:26PM +0200, Grygorii Strashko wrote: > On -RT, TI DRA7 PCIe driver always produces below backtrace when the > first PCI interrupt is triggered: > > [ cut here ] > WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150 >

[PATCH v2] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

2015-11-20 Thread Grygorii Strashko
On -RT, TI DRA7 PCIe driver always produces below backtrace when the first PCI interrupt is triggered: [ cut here ] WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150 handle_irq_event_percpu+0x14c/0x174() irq 460 handler irq_default_primary_handler+0x0/0x14 enabled