qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
	qemu-block@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PULL 00/11] Block patches
Date: Tue,  7 Sep 2021 09:13:52 +0100	[thread overview]
Message-ID: <20210907081403.816404-1-stefanha@redhat.com> (raw)

The following changes since commit 88afdc92b644120e0182c8567e1b1d236e471b12:

  Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2021-09-05 15:48:42 +0100)

are available in the Git repository at:

  https://gitlab.com/stefanha/qemu.git tags/block-pull-request

for you to fetch changes up to 9bd2788f49c331b02372cc257b11e4c984d39708:

  block/nvme: Only report VFIO error on failed retry (2021-09-07 09:08:24 +0100)

----------------------------------------------------------------
Pull request

Userspace NVMe driver patches.

----------------------------------------------------------------

Philippe Mathieu-Daudé (11):
  block/nvme: Use safer trace format string
  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()
  block/nvme: Have nvme_create_queue_pair() report errors consistently
  util/vfio-helpers: Pass Error handle to qemu_vfio_dma_map()
  util/vfio-helpers: Extract qemu_vfio_water_mark_reached()
  util/vfio-helpers: Use error_setg in qemu_vfio_find_[fixed/temp]_iova
  util/vfio-helpers: Simplify qemu_vfio_dma_map() returning directly
  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         | 99 ++++++++++++++++++++-----------------
 block/trace-events          |  2 +-
 4 files changed, 76 insertions(+), 56 deletions(-)

-- 
2.31.1




             reply	other threads:[~2021-09-07  8:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  8:13 Stefan Hajnoczi [this message]
2021-09-07  8:13 ` [PULL 01/11] block/nvme: Use safer trace format string Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 02/11] util/vfio-helpers: Let qemu_vfio_verify_mappings() use error_report() Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 03/11] util/vfio-helpers: Replace qemu_mutex_lock() calls with QEMU_LOCK_GUARD Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 04/11] util/vfio-helpers: Remove unreachable code in qemu_vfio_dma_map() Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 05/11] block/nvme: Have nvme_create_queue_pair() report errors consistently Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 06/11] util/vfio-helpers: Pass Error handle to qemu_vfio_dma_map() Stefan Hajnoczi
2021-09-07  8:13 ` [PULL 07/11] util/vfio-helpers: Extract qemu_vfio_water_mark_reached() Stefan Hajnoczi
2021-09-07  8:14 ` [PULL 08/11] util/vfio-helpers: Use error_setg in qemu_vfio_find_[fixed/temp]_iova Stefan Hajnoczi
2021-09-07  8:14 ` [PULL 09/11] util/vfio-helpers: Simplify qemu_vfio_dma_map() returning directly Stefan Hajnoczi
2021-09-07  8:14 ` [PULL 10/11] util/vfio-helpers: Let qemu_vfio_do_mapping() propagate Error Stefan Hajnoczi
2021-09-07  8:14 ` [PULL 11/11] block/nvme: Only report VFIO error on failed retry Stefan Hajnoczi
2021-09-07 15:08 ` [PULL 00/11] Block patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2020-06-05  9:47 Stefan Hajnoczi
2020-06-05 12:52 ` Peter Maydell
2019-11-05 15:43 Stefan Hajnoczi
2019-11-06 16:01 ` Peter Maydell

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=20210907081403.816404-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).