From: Bjorn Helgaas <bhelgaas@google.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, amirv@mellanox.com,
alex.williamson@redhat.com, eli@mellanox.com,
weiyang@linux.vnet.ibm.com
Subject: Re: [PATCH v3] PCI: Mark broken INTx masking for Mellanox devices
Date: Fri, 5 Sep 2014 15:38:50 -0600 [thread overview]
Message-ID: <20140905213850.GH8080@google.com> (raw)
In-Reply-To: <1407844091-20815-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Tue, Aug 12, 2014 at 09:48:11PM +1000, Gavin Shan wrote:
> The VFIO driver is routing LSI interrupts by capturing, masking,
> and then delivering. When passing though Mellanox adapters from
> host to guest, interrupt storm was reported from host and guest.
> That's because we can't mask the LSI interrupt with help of PCI
> command register.
>
> # lspci | grep Mellanox
> 0001:05:00.0 Ethernet controller: Mellanox Technologies MT27500 \
> Family [ConnectX-3]
> 0005:01:00.0 Ethernet controller: Mellanox Technologies MT26448 \
> [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0)
>
> It's confirmed by Amir Vadai that all Mellanox devices have same
> problem. The patch marks broken INTx masking for all Mellanox
> adapters.
>
> Cc: Amir Vadai <amirv@mellanox.com>
> Suggested-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
I applied this with Amir's ack to pci/virtualization for v3.18.
It's possible Mellanox will someday make a device where INTx masking works.
I guess we'll have to deal with that if and when it happens.
> ---
> v3: Mark broken INTx masking for all Mellanox adapters
> ---
> drivers/pci/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 80c2d01..da062d8 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -2985,6 +2985,8 @@ DECLARE_PCI_FIXUP_HEADER(0x1814, 0x0601, /* Ralink RT2800 802.11n PCI */
> */
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_REALTEK, 0x8169,
> quirk_broken_intx_masking);
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MELLANOX, PCI_ANY_ID,
> + quirk_broken_intx_masking);
>
> #ifdef CONFIG_ACPI
> /*
> --
> 1.8.3.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-09-05 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 11:48 [PATCH v3] PCI: Mark broken INTx masking for Mellanox devices Gavin Shan
2014-08-12 11:59 ` Amir Vadai
2014-08-26 0:58 ` Gavin Shan
2014-09-05 21:38 ` 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=20140905213850.GH8080@google.com \
--to=bhelgaas@google.com \
--cc=alex.williamson@redhat.com \
--cc=amirv@mellanox.com \
--cc=eli@mellanox.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=weiyang@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).