From: Sam Li <faithilikerun@gmail.com>
To: qemu-devel@nongnu.org
Cc: dmitry.fomichev@wdc.com, "Michael S. Tsirkin" <mst@redhat.com>,
hare@suse.de, qemu-block@nongnu.org,
damien.lemoal@opensource.wdc.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Sam Li <faithilikerun@gmail.com>
Subject: [RFC v3 0/2] Add zoned storage emulation to virtio-blk driver
Date: Sun, 16 Oct 2022 23:05:04 +0800 [thread overview]
Message-ID: <20221016150506.172675-1-faithilikerun@gmail.com> (raw)
Note: the virtio-blk headers isn't upstream in the kernel yet therefore
marked as an RFC.
v3:
- use qemuio_from_buffer to write status bit [Stefan]
- avoid using req->elem directly [Stefan]
- fix error checkings and memory leak [Stefan]
v2:
- change units of emulated zone op coresponding to block layer APIs
- modify error checking cases [Stefan, Damien]
v1:
- add zoned storage emulation
Sam Li (2):
include: update virtio_blk headers from Linux 5.19-rc2+
virtio-blk: add zoned storage emulation for zoned devices
hw/block/virtio-blk-common.c | 2 +
hw/block/virtio-blk.c | 412 +++++++++++++++++++-
include/hw/virtio/virtio-blk.h | 11 +-
include/standard-headers/linux/virtio_blk.h | 109 ++++++
4 files changed, 531 insertions(+), 3 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-16 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 15:05 Sam Li [this message]
2022-10-16 15:05 ` [RFC v3 1/2] include: update virtio_blk headers from Linux 5.19-rc2+ Sam Li
2022-10-17 0:53 ` Dmitry Fomichev
2022-10-17 2:12 ` Damien Le Moal
2022-10-16 15:05 ` [RFC v3 2/2] virtio-blk: add zoned storage emulation for zoned devices Sam Li
2022-10-17 0:59 ` Dmitry Fomichev
2022-10-18 8:56 ` Sam Li
2022-10-23 2:08 ` Dmitry Fomichev
2022-10-23 3:01 ` 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=20221016150506.172675-1-faithilikerun@gmail.com \
--to=faithilikerun@gmail.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--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).