From: Amir Vadai <amirv@mellanox.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, <linux-pci@vger.kernel.org>
Cc: <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: Tue, 12 Aug 2014 14:59:49 +0300 [thread overview]
Message-ID: <53EA01B5.5020900@mellanox.com> (raw)
In-Reply-To: <1407844091-20815-1-git-send-email-gwshan@linux.vnet.ibm.com>
On 8/12/2014 2:48 PM, 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>
> ---
> v3: Mark broken INTx masking for all Mellanox adapters
> ---
> drivers/pci/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-By: Amir Vadai <amirv@mellanox.com>
next prev parent reply other threads:[~2014-08-12 12:00 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 [this message]
2014-08-26 0:58 ` Gavin Shan
2014-09-05 21:38 ` 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=53EA01B5.5020900@mellanox.com \
--to=amirv@mellanox.com \
--cc=alex.williamson@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.