[v1] block/nvme: Rework error reporting

[PATCH 0/9] block/nvme: Rework error reporting

Philippe Mathieu-Daudé posted 9 patches 2 years, 8 months ago

Diff against v2 v3
Download series mbox

Test checkpatch passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20210824141142.1165291-1-philmd@redhat.com

There is a newer version of this series

include/qemu/vfio-helpers.h |  2 +-
block/nvme.c                | 29 +++++++++++------
util/vfio-helpers.c         | 63 +++++++++++++++++--------------------
block/trace-events          |  2 +-
4 files changed, 50 insertions(+), 46 deletions(-)

Expand all Fold all

[PATCH 0/9] block/nvme: Rework error reporting

Posted by Philippe Mathieu-Daudé 2 years, 8 months ago

Hi,

This series contains various patches sent last year with
review comments addressed, few more cleanups, and a new
patch which remove the spurious "VFIO_MAP_DMA failed: No
space left on device" now poping up since commit 15a730e7a.
(it is the expected behavior, which is why we retry the
same call after flushing the DMA mappings).

Regards,

Phil.

Philippe Mathieu-Daudé (9):
  block/nvme: Use safer trace format string
  block/nvme: Have nvme_create_queue_pair() report errors consistently
  util/vfio-helpers: Let qemu_vfio_verify_mappings() use error_report()
  util/vfio-helpers: Replace qemu_mutex_lock() calls with
    QEMU_LOCK_GUARD
  util/vfio-helpers: Remove unreachable code in qemu_vfio_dma_map()
  util/vfio-helpers: Pass Error handle to qemu_vfio_dma_map()
  util/vfio-helpers: Have qemu_vfio_dma_map() propagate Error
  util/vfio-helpers: Let qemu_vfio_do_mapping() propagate Error
  block/nvme: Only report VFIO error on failed retry

 include/qemu/vfio-helpers.h |  2 +-
 block/nvme.c                | 29 +++++++++++------
 util/vfio-helpers.c         | 63 +++++++++++++++++--------------------
 block/trace-events          |  2 +-
 4 files changed, 50 insertions(+), 46 deletions(-)

-- 
2.31.1