qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	qemu-block@nongnu.org, "Klaus Jensen" <k.jensen@samsung.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Keith Busch" <kbusch@kernel.org>,
	"Klaus Jensen" <its@irrelevant.dk>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v8 0/5] hw/block/nvme: dulbe and dsm support
Date: Thu, 12 Nov 2020 20:59:40 +0100	[thread overview]
Message-ID: <20201112195945.819915-1-its@irrelevant.dk> (raw)

From: Klaus Jensen <k.jensen@samsung.com>

This adds support for the Deallocated or Unwritten Logical Block error
recovery feature as well as the Dataset Management command.

v8:
  - Move req->opaque clearing to nvme_req_clear.
  - Add two preparation/cleanup patches.

v7:
  - Handle negative return value from bdrv_block_status.
  - bdrv_get_info may not be supported on all block drivers, so do not
    consider it a fatal error.

v6:
  - Skip the allocation of the discards integer and just use the opaque
    value directly (Philippe)
  - Split changes to include/block/nvme.h into a separate patch
    (Philippe)
  - Clean up some convoluted checks on the discards value (Philippe)
  - Use unambiguous units in the commit messages (Philippe)
  - Stack allocate the range array (Keith)

v5:
  - Restore status code from callback (Keith)

v4:
  - Removed mixed declaration and code (Keith)
  - Set NPDG and NPDA and account for the blockdev cluster size.

Klaus Jensen (5):
  hw/block/nvme: remove superfluous NvmeCtrl parameter
  hw/block/nvme: pull aio error handling
  hw/block/nvme: add dulbe support
  nvme: add namespace I/O optimization fields to shared header
  hw/block/nvme: add the dataset management command

 hw/block/nvme-ns.h    |   4 +
 hw/block/nvme.h       |   2 +
 include/block/nvme.h  |  12 +-
 hw/block/nvme-ns.c    |  34 +++++-
 hw/block/nvme.c       | 258 ++++++++++++++++++++++++++++++++++++------
 hw/block/trace-events |   4 +
 6 files changed, 276 insertions(+), 38 deletions(-)

-- 
2.29.2



             reply	other threads:[~2020-11-12 20:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 19:59 Klaus Jensen [this message]
2020-11-12 19:59 ` [PATCH v8 1/5] hw/block/nvme: remove superfluous NvmeCtrl parameter Klaus Jensen
2020-11-16 11:29   ` Minwoo Im
2020-11-12 19:59 ` [PATCH v8 2/5] hw/block/nvme: pull aio error handling Klaus Jensen
2020-11-16 11:36   ` Minwoo Im
2020-11-16 11:52     ` Klaus Jensen
2020-11-16 17:57   ` Keith Busch
2020-11-16 18:18     ` Klaus Jensen
2020-11-17  7:16       ` Klaus Jensen
2020-11-12 19:59 ` [PATCH v8 3/5] hw/block/nvme: add dulbe support Klaus Jensen
2020-11-16 11:43   ` Minwoo Im
2020-11-16 11:57     ` Klaus Jensen
2020-11-16 18:00   ` Keith Busch
2020-11-12 19:59 ` [PATCH v8 4/5] nvme: add namespace I/O optimization fields to shared header Klaus Jensen
2020-11-16 11:47   ` Minwoo Im
2020-11-12 19:59 ` [PATCH v8 5/5] hw/block/nvme: add the dataset management command Klaus Jensen
2020-11-16 18:01   ` Keith Busch
2020-11-23 20:45 ` [PATCH v8 0/5] hw/block/nvme: dulbe and dsm support Klaus Jensen

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=20201112195945.819915-1-its@irrelevant.dk \
    --to=its@irrelevant.dk \
    --cc=k.jensen@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --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).