From: Sam Li <faithilikerun@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
stefanha@redhat.com, "Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
dmitry.fomichev@wdc.com, hare@suse.de,
"Hanna Reitz" <hreitz@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
dlemoal@kernel.org, "Keith Busch" <kbusch@kernel.org>,
"Klaus Jensen" <its@irrelevant.dk>,
"Sam Li" <faithilikerun@gmail.com>
Subject: [RFC v3 1/7] docs/qcow2: add zd_extension_size option to the zoned format feature
Date: Mon, 22 Jan 2024 20:00:07 +0100 [thread overview]
Message-ID: <20240122190013.41302-2-faithilikerun@gmail.com> (raw)
In-Reply-To: <20240122190013.41302-1-faithilikerun@gmail.com>
The NVMe ZNS command set has the zone descriptor extension feature for
associating the data to a zone. Devices that supports ZAC/ZBC have zero
zone descriptor extension size.
Signed-off-by: Sam Li <faithilikerun@gmail.com>
---
docs/interop/qcow2.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
index a8dd4c3b15..106477d9ad 100644
--- a/docs/interop/qcow2.txt
+++ b/docs/interop/qcow2.txt
@@ -436,6 +436,15 @@ The fields of the zoned extension are:
The offset of zoned metadata structure in the contained
image, in bytes.
+ 44 - 51: zd_extension_size
+ The size of zone descriptor extension data in bytes.
+ The value must be a multiple of 64.
+
+ The zone descriptor extension feature is associating data
+ to a zone which is only available in the NVMe ZNS command
+ set. A value of zero indicates the feature is not
+ available.
+
== Full disk encryption header pointer ==
The full disk encryption header must be present if, and only if, the
--
2.40.1
next prev parent reply other threads:[~2024-01-22 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 19:00 [RFC v3 0/7] Add persistence to NVMe ZNS emulation Sam Li
2024-01-22 19:00 ` Sam Li [this message]
2024-01-22 19:00 ` [RFC v3 2/7] qcow2: add zd_extension configurations to zoned metadata Sam Li
2024-01-22 19:00 ` [RFC v3 3/7] hw/nvme: use blk_get_*() to access zone info in the block layer Sam Li
2024-01-22 19:00 ` [RFC v3 4/7] hw/nvme: add blk_get_zone_extension to access zd_extensions Sam Li
2024-01-22 19:00 ` [RFC v3 5/7] hw/nvme: make the metadata of ZNS emulation persistent Sam Li
2024-01-22 19:00 ` [RFC v3 6/7] hw/nvme: refactor zone append write using block layer APIs Sam Li
2024-01-22 19:00 ` [RFC v3 7/7] hw/nvme: make ZDED persistent Sam Li
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=20240122190013.41302-2-faithilikerun@gmail.com \
--to=faithilikerun@gmail.com \
--cc=armbru@redhat.com \
--cc=david@redhat.com \
--cc=dlemoal@kernel.org \
--cc=dmitry.fomichev@wdc.com \
--cc=eblake@redhat.com \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--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 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).