From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
alex.williamson@redhat.com, pbonzini@redhat.com
Cc: thuth@redhat.com, qemu-devel@nongnu.org,
mdroth@linux.vnet.ibm.com, aik@ozlabs.ru, abologna@redhat.com,
gwshan@linux.vnet.ibm.com, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3 2/7] vfio: Generalize vfio_listener_region_add failure path
Date: Wed, 30 Sep 2015 10:20:45 +0200 [thread overview]
Message-ID: <560B9B5D.7010509@redhat.com> (raw)
In-Reply-To: <1443579237-9636-3-git-send-email-david@gibson.dropbear.id.au>
On 30/09/2015 04:13, David Gibson wrote:
> If a DMA mapping operation fails in vfio_listener_region_add() it
> checks to see if we've already completed initial setup of the
> container. If so it reports an error so the setup code can fail
> gracefully, otherwise throws a hw_error().
>
> There are other potential failure cases in vfio_listener_region_add()
> which could benefit from the same logic, so move it to its own
> fail: block. Later patches can use this to extend other failure cases
> to fail as gracefully as possible under the circumstances.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Reviewed-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/vfio/common.c | 26 +++++++++++++++-----------
> 1 file changed, 15 insertions(+), 11 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 1545f62..95a4850 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -399,19 +399,23 @@ static void vfio_listener_region_add(MemoryListener *listener,
> error_report("vfio_dma_map(%p, 0x%"HWADDR_PRIx", "
> "0x%"HWADDR_PRIx", %p) = %d (%m)",
> container, iova, end - iova, vaddr, ret);
> + goto fail;
> + }
>
> - /*
> - * On the initfn path, store the first error in the container so we
> - * can gracefully fail. Runtime, there's not much we can do other
> - * than throw a hardware error.
> - */
> - if (!container->initialized) {
> - if (!container->error) {
> - container->error = ret;
> - }
> - } else {
> - hw_error("vfio: DMA mapping failed, unable to continue");
> + return;
> +
> +fail:
> + /*
> + * On the initfn path, store the first error in the container so we
> + * can gracefully fail. Runtime, there's not much we can do other
> + * than throw a hardware error.
> + */
> + if (!container->initialized) {
> + if (!container->error) {
> + container->error = ret;
> }
> + } else {
> + hw_error("vfio: DMA mapping failed, unable to continue");
> }
> }
>
>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
next prev parent reply other threads:[~2015-09-30 8:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 2:13 [Qemu-devel] [PATCHv3 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge David Gibson
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 1/7] vfio: Remove unneeded union from VFIOContainer David Gibson
2015-09-30 8:19 ` Laurent Vivier
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 2/7] vfio: Generalize vfio_listener_region_add failure path David Gibson
2015-09-30 8:20 ` Laurent Vivier [this message]
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 3/7] vfio: Check guest IOVA ranges against host IOMMU capabilities David Gibson
2015-09-30 8:25 ` Laurent Vivier
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 4/7] vfio: Record host IOMMU's available IO page sizes David Gibson
2015-09-30 8:27 ` Laurent Vivier
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 5/7] memory: Allow replay of IOMMU mapping notifications David Gibson
2015-09-30 8:32 ` Laurent Vivier
2015-09-30 8:59 ` Laurent Vivier
2015-09-30 23:51 ` David Gibson
2015-10-05 13:21 ` Paolo Bonzini
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 6/7] vfio: Allow hotplug of containers onto existing guest IOMMU mappings David Gibson
2015-09-30 9:09 ` Laurent Vivier
2015-09-30 23:56 ` David Gibson
2015-09-30 2:13 ` [Qemu-devel] [PATCHv3 7/7] vfio: Expose a VFIO PCI device's group for EEH David Gibson
2015-09-30 9:12 ` Laurent Vivier
2015-10-02 18:12 ` [Qemu-devel] [PATCHv3 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge 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=560B9B5D.7010509@redhat.com \
--to=lvivier@redhat.com \
--cc=abologna@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=gwshan@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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.