From: Marc Zyngier <marc.zyngier@arm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Phil Edworthy <phil.edworthy@renesas.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: MSI: Only use the generic MSI layer when domain is hierarchical
Date: Fri, 4 Dec 2015 08:13:50 +0000 [thread overview]
Message-ID: <20151204081350.2113b7e6@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20151204002758.GA10479@localhost>
On Thu, 3 Dec 2015 18:27:59 -0600
Bjorn Helgaas <helgaas@kernel.org> wrote:
> On Mon, Nov 30, 2015 at 10:25:34AM +0000, Phil Edworthy wrote:
> > Cc'd linux-pci ml
> >
> > On 23 November 2015 14:27, Marc Zyngier wrote:
> >
> > Since d8a1cb757550 ("PCI/MSI: Let pci_msi_get_domain use struct
> > device::msi_domain"), we use the MSI domain associated to the PCI device.
> >
> > But finding a MSI domain doesn't mean that the domain is implemented
> > using the generic MSI domain API, and a number of MSI controllers
> > are still using the arch_setup_msi_irq/arch_teardown_msi_irqs.
> >
> > In order to avoid a firework on these systems, check that the domain
> > we just obtained is hierarchical. If not, don't use the generic MSI
> > stuff and stick with the old one. Not pretty, but reliable.
> >
> > Another insentive to rework those drivers and phase out this API.
> >
> > Reported-by: Phil Edworthy <phil.edworthy@renesas.com>
> > Tested-by: Phil Edworthy <phil.edworthy@renesas.com>
> > Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>
> Thanks, I applied this with Thomas' ack to pci/msi for v4.5.
>
> It looks like d8a1cb757550 appeared in v4.3. Is this a fix for that
> commit? Does this need to be backported via a stable tag?
Hi Bjorn,
I think this really deserves to be queued as an immediate fix for 4.4
rather than 4.5, as some systems in mainline are affected by this bug:
http://www.spinics.net/lists/arm-kernel/msg465792.html
It would also deserve a stable tag for 4.3.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2015-12-04 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 14:27 Marc Zyngier
2015-11-23 17:38 ` Thomas Gleixner
2015-12-03 16:43 ` Marc Zyngier
2015-11-30 10:25 ` Phil Edworthy
2015-12-04 0:27 ` Bjorn Helgaas
2015-12-04 8:13 ` Marc Zyngier [this message]
2015-12-04 16:17 ` Bjorn Helgaas
2015-12-04 17:07 ` Marc Zyngier
2015-12-04 17:46 ` Bjorn Helgaas
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=20151204081350.2113b7e6@why.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=phil.edworthy@renesas.com \
--cc=tglx@linutronix.de \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®