From: Bjorn Helgaas <helgaas@kernel.org>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: bhelgaas@google.com, jingoohan1@gmail.com,
Joao.Pinto@synopsys.com, svarbanov@mm-sol.com,
keith.busch@intel.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] PCI: dwc/host: Mark PCIe/PCI (MSI) cascade ISR as IRQF_NO_THREAD
Date: Tue, 23 May 2017 13:57:18 -0500 [thread overview]
Message-ID: <20170523185718.GC2637@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20170420102718.3778-1-jszhang@marvell.com>
On Thu, Apr 20, 2017 at 06:27:18PM +0800, Jisheng Zhang wrote:
> Similar as commit 8ff0ef996ca0 ("PCI: host: Mark PCIe/PCI (MSI) IRQ
> cascade handlers as IRQF_NO_THREAD"), we should mark PCIe/PCI (MSI)
> IRQ cascade handlers IRQF_NO_THREAD explicitly. I just found this
> issue in pcie-designware-plat driver, then searched the code, I think
> we should fix pcie-qcom and vmd as well.
>
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Applied with ack/reviewed-by from Jingoo and Keith to pci/host-designware
for v4.13, thanks!
> ---
> drivers/pci/dwc/pcie-designware-plat.c | 3 ++-
> drivers/pci/dwc/pcie-qcom.c | 3 ++-
> drivers/pci/host/vmd.c | 3 ++-
> 3 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/pci/dwc/pcie-designware-plat.c b/drivers/pci/dwc/pcie-designware-plat.c
> index f20d494922ab..0db1dafc82bb 100644
> --- a/drivers/pci/dwc/pcie-designware-plat.c
> +++ b/drivers/pci/dwc/pcie-designware-plat.c
> @@ -67,7 +67,8 @@ static int dw_plat_add_pcie_port(struct pcie_port *pp,
>
> ret = devm_request_irq(dev, pp->msi_irq,
> dw_plat_pcie_msi_irq_handler,
> - IRQF_SHARED, "dw-plat-pcie-msi", pp);
> + IRQF_SHARED | IRQF_NO_THREAD,
> + "dw-plat-pcie-msi", pp);
> if (ret) {
> dev_err(dev, "failed to request MSI IRQ\n");
> return ret;
> diff --git a/drivers/pci/dwc/pcie-qcom.c b/drivers/pci/dwc/pcie-qcom.c
> index 67eb7f5926dd..a5570c58081e 100644
> --- a/drivers/pci/dwc/pcie-qcom.c
> +++ b/drivers/pci/dwc/pcie-qcom.c
> @@ -727,7 +727,8 @@ static int qcom_pcie_probe(struct platform_device *pdev)
>
> ret = devm_request_irq(dev, pp->msi_irq,
> qcom_pcie_msi_irq_handler,
> - IRQF_SHARED, "qcom-pcie-msi", pp);
> + IRQF_SHARED | IRQF_NO_THREAD,
> + "qcom-pcie-msi", pp);
> if (ret) {
> dev_err(dev, "cannot request msi irq\n");
> return ret;
> diff --git a/drivers/pci/host/vmd.c b/drivers/pci/host/vmd.c
> index e27ad2a3bd33..784f63beb487 100644
> --- a/drivers/pci/host/vmd.c
> +++ b/drivers/pci/host/vmd.c
> @@ -704,7 +704,8 @@ static int vmd_probe(struct pci_dev *dev, const struct pci_device_id *id)
>
> INIT_LIST_HEAD(&vmd->irqs[i].irq_list);
> err = devm_request_irq(&dev->dev, pci_irq_vector(dev, i),
> - vmd_irq, 0, "vmd", &vmd->irqs[i]);
> + vmd_irq, IRQF_NO_THREAD,
> + "vmd", &vmd->irqs[i]);
> if (err)
> return err;
> }
> --
> 2.11.0
>
prev parent reply other threads:[~2017-05-23 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 10:27 Jisheng Zhang
2017-04-20 15:07 ` Jingoo Han
2017-04-20 15:20 ` Keith Busch
2017-05-23 18:57 ` Bjorn Helgaas [this message]
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=20170523185718.GC2637@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=jszhang@marvell.com \
--cc=keith.busch@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=svarbanov@mm-sol.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
all inboxes | Powered by JetHome®