From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, alex.williamson@redhat.com, aik@ozlabs.ru
Subject: Re: [PATCH 3/3] drivers/vfio/pci: Fix MSIx message lost
Date: Mon, 03 Mar 2014 14:51:50 +1100 [thread overview]
Message-ID: <1393818710.10727.22.camel@pasglop> (raw)
In-Reply-To: <1393817042-13758-3-git-send-email-shangw@linux.vnet.ibm.com>
On Mon, 2014-03-03 at 11:24 +0800, Gavin Shan wrote:
> The problem is specific to the case of BIST issued applied to IPR
> adapter on the guest side. After BIST reset, we lose everything
> in MSIx table and we never have chance update MSIx messages for
> those enabled interrupts to MSIx table.
>
> The patch fixes it by writing MSIx message to MSIx table before
> reenabling them.
That needs a better explanation... the guest does try to restore the
MSI-X (in a way similar to resuming from suspend) by writing the
message value back into the table.
My understanding is that we trap that and turn that into a call to
vfio_msi_set_vector_signal, is that correct ?
In that case, it does indeed make sense to have that function rewrite
the cached message.
(Just trying to understand how this patch fixes the problem we saw)
I suppose other drivers would have similar issues if they have some
kind of internal "reset" path and try to save and restore the MSI-X
table.
Cheers,
Ben.
> Reported-by: Wen Xiong <wenxiong@us.ibm.com>
> Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
> ---
> drivers/vfio/pci/vfio_pci_intrs.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
> index 2103576..279ebd0 100644
> --- a/drivers/vfio/pci/vfio_pci_intrs.c
> +++ b/drivers/vfio/pci/vfio_pci_intrs.c
> @@ -17,6 +17,7 @@
> #include <linux/interrupt.h>
> #include <linux/eventfd.h>
> #include <linux/pci.h>
> +#include <linux/msi.h>
> #include <linux/file.h>
> #include <linux/poll.h>
> #include <linux/vfio.h>
> @@ -517,6 +518,7 @@ static int vfio_msi_set_vector_signal(struct vfio_pci_device *vdev,
> struct pci_dev *pdev = vdev->pdev;
> int irq = msix ? vdev->msix[vector].vector : pdev->irq + vector;
> char *name = msix ? "vfio-msix" : "vfio-msi";
> + struct msi_msg msg;
> struct eventfd_ctx *trigger;
> int ret;
>
> @@ -544,6 +546,23 @@ static int vfio_msi_set_vector_signal(struct vfio_pci_device *vdev,
> return PTR_ERR(trigger);
> }
>
> + /* We possiblly lose the MSI/MSIx message in some cases.
> + * For example, BIST reset on IPR adapter. The MSIx table
> + * is cleaned out. However, we never get chance to put
> + * MSIx messages to MSIx table because all MSIx stuff is
> + * being cached in QEMU. Here, we had the trick to put the
> + * MSI/MSIx message back.
> + *
> + * Basically, we needn't worry about MSI messages. However,
> + * it's not harmful and there might be cases of PCI config data
> + * lost because of cached PCI config data in QEMU again.
> + *
> + * Note that we should flash the message prior to enabling
> + * the corresponding interrupt by request_irq().
> + */
> + 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) {
next prev parent reply other threads:[~2014-03-03 3:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 3:24 [PATCH 1/3] drivers/vfio: Rework offsetofend() Gavin Shan
2014-03-03 3:24 ` [PATCH 2/3] drivers/vfio/pci: Fix wrong MSI interrupt count Gavin Shan
2014-03-03 4:17 ` Alex Williamson
2014-03-03 3:24 ` [PATCH 3/3] drivers/vfio/pci: Fix MSIx message lost Gavin Shan
2014-03-03 3:51 ` Benjamin Herrenschmidt [this message]
2014-03-03 4:43 ` Alexey Kardashevskiy
2014-03-03 5:00 ` Benjamin Herrenschmidt
2014-03-03 4:49 ` Alex Williamson
2014-03-03 5:05 ` Benjamin Herrenschmidt
[not found] ` <20140303061036.GA4447@shangw.(null)>
2014-03-03 19:36 ` Alex Williamson
[not found] ` <20140304023018.GA21672@shangw.(null)>
2014-03-04 20:45 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 5:46 [PATCH 0/3] VFIO Bug Fixes Gavin Shan
2014-03-10 5:46 ` [PATCH 3/3] drivers/vfio/pci: Fix MSIx message lost Gavin Shan
2014-03-17 22:16 ` Alex Williamson
[not found] ` <20140318013238.GA9843@shangw.(null)>
2014-03-18 22:44 ` Alex Williamson
2014-04-02 1:16 ` Alexey Kardashevskiy
2014-04-02 1:36 ` Alex Williamson
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=1393818710.10727.22.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=shangw@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.