From: Alberto Faria <afaria@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Xie Yongji" <xieyongji@bytedance.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Raphael Norwitz" <raphael@enfabrica.net>,
"Cornelia Huck" <cohuck@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
qemu-block@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Zhao Liu" <zhao1.liu@intel.com>, "Coiby Xu" <Coiby.Xu@gmail.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Alberto Faria" <afaria@redhat.com>
Subject: [RFC v2 0/4] virtio-blk: Add support for FUA write requests
Date: Thu, 8 May 2025 17:20:40 +0100 [thread overview]
Message-ID: <20250508162044.857655-1-afaria@redhat.com> (raw)
There is a proposal to introduce virtio-blk fua write support to the virtio
spec [1], and a matching kernel RFC [2]. This series implements the proposal by
adding VIRTIO_BLK_{F,T}_OUT_FUA uapi definitions and corresponding virtio-blk,
vhost-user-blk, and vduse-blk support.
[1] https://lore.kernel.org/virtio-comment/20250507152602.3993258-1-afaria@redhat.com/
[2] https://lore.kernel.org/linux-block/20250508001951.421467-1-afaria@redhat.com/
v2:
- Include missing hw/block/virtio-blk.c changes actually implementing
VIRTIO_BLK_T_OUT_FUA support.
Alberto Faria (4):
include: Add tentative virtio-blk FUA write definitions
virtio-blk: Add VIRTIO_BLK_T_OUT_FUA command support
vhost-user-blk: Add VIRTIO_BLK_T_OUT_FUA command support
vduse-blk: Add VIRTIO_BLK_T_OUT_FUA command support
block/export/vduse-blk.c | 3 +-
block/export/vhost-user-blk-server.c | 1 +
block/export/virtio-blk-handler.c | 7 ++-
contrib/vhost-user-blk/vhost-user-blk.c | 16 ++++--
hw/block/vhost-user-blk.c | 3 ++
hw/block/virtio-blk.c | 41 +++++++--------
hw/core/machine.c | 5 +-
hw/virtio/virtio-qmp.c | 2 +
include/hw/virtio/virtio-blk.h | 1 +
include/standard-headers/linux/virtio_blk.h | 4 ++
tests/qtest/vhost-user-blk-test.c | 56 +++++++++++++++++++++
tests/qtest/virtio-blk-test.c | 56 +++++++++++++++++++++
12 files changed, 168 insertions(+), 27 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-08 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 16:20 Alberto Faria [this message]
2025-05-08 16:20 ` [RFC v2 1/4] include: Add tentative virtio-blk FUA write definitions Alberto Faria
2025-05-12 19:12 ` Stefan Hajnoczi
2025-05-08 16:20 ` [RFC v2 2/4] virtio-blk: Add VIRTIO_BLK_T_OUT_FUA command support Alberto Faria
2025-05-12 19:32 ` Stefan Hajnoczi
2025-05-08 16:20 ` [RFC v2 3/4] vhost-user-blk: " Alberto Faria
2025-05-12 19:43 ` Stefan Hajnoczi
2025-05-08 16:20 ` [RFC v2 4/4] vduse-blk: " Alberto Faria
2025-05-12 19:52 ` Stefan Hajnoczi
2025-05-12 19:52 ` Stefan Hajnoczi
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=20250508162044.857655-1-afaria@redhat.com \
--to=afaria@redhat.com \
--cc=Coiby.Xu@gmail.com \
--cc=cohuck@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael@enfabrica.net \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=wangyanan55@huawei.com \
--cc=xieyongji@bytedance.com \
--cc=zhao1.liu@intel.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).