From: Stefan Hajnoczi <stefanha@redhat.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Hanna Reitz <hreitz@redhat.com>,
damien.lemoal@opensource.wdc.com, hare@suse.de,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
dmitry.fomichev@wdc.com
Subject: Re: [RFC v5 0/3] Add zoned storage emulation to virtio-blk driver
Date: Tue, 20 Dec 2022 16:05:17 -0500 [thread overview]
Message-ID: <Y6IjjRFUxtHHbh5K@fedora> (raw)
In-Reply-To: <20221219081644.11790-1-faithilikerun@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
On Mon, Dec 19, 2022 at 04:16:41PM +0800, Sam Li wrote:
> Note: the virtio-blk headers isn't upstream in the kernel yet therefore
> marked as an RFC. More information can be found here:
> https://patchwork.kernel.org/project/linux-block/cover/20221030043545.974223-1-dmitry.fomichev@wdc.com/
The VIRTIO spec changes have been merged. The Linux virtio_blk guest
driver patches are in Michael Tsirkin's vhost tree:
https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/tree/drivers/block/virtio_blk.c?h=vhost
The "RFC" can be dropped as soon as Linus merges the changes. Almost
there!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-12-20 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 8:16 [RFC v5 0/3] Add zoned storage emulation to virtio-blk driver Sam Li
2022-12-19 8:16 ` [RFC v5 1/3] include: update virtio_blk headers Sam Li
2022-12-19 8:16 ` [RFC v5 2/3] virtio-blk: add zoned storage emulation for zoned devices Sam Li
2022-12-20 21:37 ` Stefan Hajnoczi
2022-12-21 4:06 ` Sam Li
2022-12-19 8:16 ` [RFC v5 3/3] virtio-blk: add some trace events for zoned emulation Sam Li
2022-12-20 21:05 ` Stefan Hajnoczi [this message]
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=Y6IjjRFUxtHHbh5K@fedora \
--to=stefanha@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=faithilikerun@gmail.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 \
/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.