From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
"Klaus Jensen" <k.jensen@samsung.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Klaus Jensen" <its@irrelevant.dk>,
"Hanna Reitz" <hreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Keith Busch" <kbusch@kernel.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v2 0/3] hw/nvme: zoned random write area
Date: Thu, 27 Jan 2022 09:19:47 +0100 [thread overview]
Message-ID: <20220127081950.953572-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
This series adds support for a zoned random write area as standardized
in TP 4076 ("Zoned Random Write Area").
v2:
* fixed rsvd member in NvmeZoneSendCmd (Keith)
* dropped patch 2 ("hw/nvme: add zone attribute get/set helpers")
* amended patch 4 to open code the helpers removed from patch 2
Klaus Jensen (3):
hw/nvme: add struct for zone management send
hw/nvme: add ozcs enum
hw/nvme: add support for zoned random write area
hw/nvme/ctrl.c | 181 +++++++++++++++++++++++++++++++++++++------
hw/nvme/ns.c | 61 ++++++++++++++-
hw/nvme/nvme.h | 10 +++
hw/nvme/trace-events | 1 +
include/block/nvme.h | 40 +++++++++-
5 files changed, 266 insertions(+), 27 deletions(-)
--
2.35.0
next reply other threads:[~2022-01-27 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 8:19 Klaus Jensen [this message]
2022-01-27 8:19 ` [PATCH v2 1/3] hw/nvme: add struct for zone management send Klaus Jensen
2022-01-27 8:19 ` [PATCH v2 2/3] hw/nvme: add ozcs enum Klaus Jensen
2022-01-27 8:19 ` [PATCH v2 3/3] hw/nvme: add support for zoned random write area Klaus Jensen
2022-02-03 20:49 ` [PATCH v2 0/3] hw/nvme: " 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=20220127081950.953572-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.