From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, alex.williamson@redhat.com,
bhelgaas@google.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH 4/4] vfio/pci: Restore MSIx message prior to enabling
Date: Mon, 19 May 2014 12:54:22 +1000 [thread overview]
Message-ID: <20140519025422.GA2253@shangw> (raw)
In-Reply-To: <1399944924-1200-5-git-send-email-gwshan@linux.vnet.ibm.com>
On Tue, May 13, 2014 at 11:35:24AM +1000, Gavin Shan wrote:
>The MSIx vector table lives in device memory, which may be cleared as
>part of a backdoor device reset. This is the case on the IBM IPR HBA
>when the BIST is run on the device. When assigned to a QEMU guest,
>the guest driver does a pci_save_state(), issues a BIST, then does a
>pci_restore_state(). The BIST clears the MSIx vector table, but due
>to the way interrupts are configured the pci_restore_state() does not
>restore the vector table as expected. Eventually this results in an
>EEH error on Power platforms when the device attempts to signal an
>interrupt with the zero'd table entry.
>
>Fix the problem by restoring the host cached MSI message prior to
>enabling each vector.
>
>Reported-by: Wen Xiong <wenxiong@linux.vnet.ibm.com>
>Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>---
Sorry about that the following line was missed. I'll add that and send
"v3" out.
#include <linux/msi.h>
> drivers/vfio/pci/vfio_pci_intrs.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
>diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
>index 9dd49c9..409346f 100644
>--- a/drivers/vfio/pci/vfio_pci_intrs.c
>+++ b/drivers/vfio/pci/vfio_pci_intrs.c
>@@ -548,6 +548,20 @@ static int vfio_msi_set_vector_signal(struct vfio_pci_device *vdev,
> return PTR_ERR(trigger);
> }
>
>+ /*
>+ * The MSIx vector table resides in device memory which may be cleared
>+ * via backdoor resets. We don't allow direct access to the vector
>+ * table so even if a userspace driver attempts to save/restore around
>+ * such a reset it would be unsuccessful. To avoid this, restore the
>+ * cached value of the message prior to enabling.
>+ */
>+ if (msix) {
>+ struct msi_msg msg;
>+
>+ get_cached_msi_msg(irq, &msg);
>+ write_msi_msg(irq, &msg);
>+ }
>+
> ret = request_irq(irq, vfio_msihandler, 0,
> vdev->ctx[vector].name, trigger);
> if (ret) {
Thanks,
Gavin
next prev parent reply other threads:[~2014-05-19 2:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 1:35 [PATCH v2 0/4] VFIO Misc fixes Gavin Shan
2014-05-13 1:35 ` [PATCH 1/4] PCI: Export MSI message relevant functions Gavin Shan
2014-05-13 1:35 ` [PATCH 2/4] drivers/vfio: Rework offsetofend() Gavin Shan
2014-05-13 1:35 ` [PATCH 3/4] drivers/vfio/pci: Fix wrong MSI interrupt count Gavin Shan
2014-05-13 1:35 ` [PATCH 4/4] vfio/pci: Restore MSIx message prior to enabling Gavin Shan
2014-05-19 2:54 ` Gavin Shan [this message]
2014-05-19 3:01 [PATCH 0/4] VFIO Misc fixes Gavin Shan
2014-05-19 3:01 ` [PATCH 4/4] vfio/pci: Restore MSIx message prior to enabling Gavin Shan
2014-05-30 22:12 ` Bjorn Helgaas
2014-05-31 11:42 ` Gavin Shan
2014-06-02 16:57 ` Bjorn Helgaas
2014-06-05 5:51 ` Gavin Shan
2014-09-10 8:13 ` Gavin Shan
2014-09-26 3:19 ` Gavin Shan
2014-09-26 3:46 ` Alex Williamson
2014-09-27 5:33 ` Gavin Shan
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=20140519025422.GA2253@shangw \
--to=gwshan@linux.vnet.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).