From: Alex Williamson <alex.williamson@redhat.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v2 2/2] VFIO: Clear stale MSIx table during EEH reset
Date: Tue, 02 Sep 2014 14:10:42 -0600 [thread overview]
Message-ID: <1409688642.3804.114.camel@ul30vt.home> (raw)
In-Reply-To: <1409532812-8644-3-git-send-email-gwshan@linux.vnet.ibm.com>
On Mon, 2014-09-01 at 10:53 +1000, Gavin Shan wrote:
> The PCI device MSIx table is cleaned out in hardware after EEH PE
> reset. However, we still hold the stale MSIx entries in QEMU, which
> should be cleared accordingly. Otherwise, we will run into another
> (recursive) EEH error and the PCI devices contained in the PE have
> to be offlined exceptionally.
>
> The patch clears stale MSIx table before EEH PE reset so that MSIx
> table could be restored properly after EEH PE reset.
>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> ---
> hw/misc/vfio.c | 32 +++++++++++++++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
> index 1a3e7eb..1f55051 100644
> --- a/hw/misc/vfio.c
> +++ b/hw/misc/vfio.c
> @@ -2724,6 +2724,17 @@ static void vfio_disable_interrupts(VFIODevice *vdev)
> }
> }
>
> +static void vfio_disable_and_reset_interrupts(VFIODevice *vdev)
> +{
> + vfio_disable_interrupts(vdev);
> +
> + switch (vdev->interrupt) {
> + case VFIO_INT_MSIX:
> + msix_reset(&vdev->pdev);
> + break;
> + }
This is apparently untested because vdev->interrupt should never be set
to VFIO_INT_MSIX after vfio_disable_interrupts(). Also, you need to
update the normal reset path to call msix_reset() unless it's already
happening via another reset handler. Thanks,
Alex
> +}
> +
> static int vfio_setup_msi(VFIODevice *vdev, int pos)
> {
> uint16_t ctrl;
> @@ -4442,8 +4453,27 @@ int vfio_container_ioctl(AddressSpace *as, int32_t groupid,
> switch (req) {
> case VFIO_CHECK_EXTENSION:
> case VFIO_IOMMU_SPAPR_TCE_GET_INFO:
> - case VFIO_EEH_PE_OP:
> break;
> + case VFIO_EEH_PE_OP: {
> + VFIODevice *vdev;
> + struct vfio_eeh_pe_op *arg = (struct vfio_eeh_pe_op *)param;
> +
> + switch (arg->op) {
> + case VFIO_EEH_PE_RESET_HOT:
> + case VFIO_EEH_PE_RESET_FUNDAMENTAL:
> + /*
> + * The MSIx table will be cleaned out by reset. We need
> + * disable it so that it can be reenabled properly. Also,
> + * the cached MSIx table should be cleared as it's not
> + * reflecting the contents in hardware.
> + */
> + QLIST_FOREACH(vdev, &group->device_list, next) {
> + vfio_disable_and_reset_interrupts(vdev);
> + }
> + }
> +
> + break;
> + }
> default:
> /* Return an error on unknown requests */
> error_report("vfio: unsupported ioctl %X", req);
next prev parent reply other threads:[~2014-09-02 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 0:53 [Qemu-devel] [RFC PATCH v2 0/2] Fix MSIx lost after PE reset Gavin Shan
2014-09-01 0:53 ` [Qemu-devel] [RFC PATCH v2 1/2] VFIO: Drop vfio_container_do_ioctl() Gavin Shan
2014-09-01 0:53 ` [Qemu-devel] [RFC PATCH v2 2/2] VFIO: Clear stale MSIx table during EEH reset Gavin Shan
2014-09-02 20:10 ` Alex Williamson [this message]
2014-09-02 23:12 ` 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=1409688642.3804.114.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=gwshan@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).