From: Markus Armbruster <armbru@redhat.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com,
"Klaus Jensen" <its@irrelevant.dk>,
qemu-block@nongnu.org, hare@suse.de,
"David Hildenbrand" <david@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Keith Busch" <kbusch@kernel.org>,
"Hanna Reitz" <hreitz@redhat.com>,
dmitry.fomichev@wdc.com, "Kevin Wolf" <kwolf@redhat.com>,
"Eric Blake" <eblake@redhat.com>, "Peter Xu" <peterx@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
dlemoal@kernel.org
Subject: Re: [RFC v2 0/7] Add persistence to NVMe ZNS emulation
Date: Thu, 30 Nov 2023 11:11:31 +0100 [thread overview]
Message-ID: <874jh3czzg.fsf@pond.sub.org> (raw)
In-Reply-To: <20231127085641.3729-1-faithilikerun@gmail.com> (Sam Li's message of "Mon, 27 Nov 2023 16:56:34 +0800")
Sam Li <faithilikerun@gmail.com> writes:
> ZNS emulation follows NVMe ZNS spec but the state of namespace
> zones does not persist accross restarts of QEMU. This patch makes the
> metadata of ZNS emulation persistent by using new block layer APIs and
> the qcow2 img as backing file. It is the second part after the patches
> - adding full zoned storage emulation to qcow2 driver.
> https://patchwork.kernel.org/project/qemu-devel/cover/20231127043703.49489-1-faithilikerun@gmail.com/
In the future, also add this information the machine-readable way,
i.e. like
Based-on: <20231127043703.49489-1-faithilikerun@gmail.com>
However, it doesn't apply on top of that series for me. Got something I
could pull?
[...]
next prev parent reply other threads:[~2023-11-30 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 8:56 [RFC v2 0/7] Add persistence to NVMe ZNS emulation Sam Li
2023-11-27 8:56 ` [RFC v2 1/7] docs/qcow2: add zd_extension_size option to the zoned format feature Sam Li
2023-11-30 10:05 ` Markus Armbruster
2023-11-27 8:56 ` [RFC v2 2/7] qcow2: add zd_extension configurations to zoned metadata Sam Li
2023-11-30 10:12 ` Markus Armbruster
2023-11-27 8:56 ` [RFC v2 3/7] hw/nvme: use blk_get_*() to access zone info in the block layer Sam Li
2023-11-27 8:56 ` [RFC v2 4/7] hw/nvme: add blk_get_zone_extension to access zd_extensions Sam Li
2023-11-27 8:56 ` [RFC v2 5/7] hw/nvme: make the metadata of ZNS emulation persistent Sam Li
2023-11-27 8:56 ` [RFC v2 6/7] hw/nvme: refactor zone append write using block layer APIs Sam Li
2023-11-27 8:56 ` [RFC v2 7/7] hw/nvme: make ZDED persistent Sam Li
2023-11-30 10:11 ` Markus Armbruster [this message]
2023-11-30 10:20 ` [RFC v2 0/7] Add persistence to NVMe ZNS emulation Sam Li
2024-01-10 6:52 ` Klaus Jensen
2024-01-22 18:43 ` Sam Li
-- strict thread matches above, loose matches on Subject: below --
2023-11-27 8:33 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=874jh3czzg.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=david@redhat.com \
--cc=dlemoal@kernel.org \
--cc=dmitry.fomichev@wdc.com \
--cc=eblake@redhat.com \
--cc=faithilikerun@gmail.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 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.