From: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
To: svt-core@virtuozzo.com
Cc: den@openvz.org, andrey.drobyshev@virtuozzo.com
Subject: [QEMU HCI-8.0 PATCH v2 0/5] vhost-blk change backend setup
Date: Fri, 4 Sep 2026 16:21:50 +0300 [thread overview]
Message-ID: <20260904132155.180581-1-andrey.zhadchenko@virtuozzo.com> (raw)
This series changes vhost-blk backend setup from block node to
a path to the device.
Getting fd from block node was a hack in the first place. It
looked ugly and broke encapsulation.
Change vhost-blk to have it's own property so it opens and owns
the descriptor.
Patches #4 implement auto-resize by watching netlink. The descripor
comes prepared with some filter from outside.
v2:
patch#1
- old patch dropped
patch#2
- moved double close fix to new 'do not double close vhostfd' patch
- dropped DEFINE_BLOCK_PROPERTIES_BASE exposition to the outside. Let's
just use defaults for now. We can later check if tweaking this values
makes any difference and add them back.
- change vhost_blk_update_size() to return zero or error and move 'changed'
to a separate argument
- changed lseek to BLKGETSIZE64 (we already use BLKROGET anyway)
patch#3
- check BLKROGET only if rw was requested
patch#4
- rework patch a bit: now we expect opened and filtered fd from
libvirt.
patch#5
- old one dropped, setup moved to libvirt
- added new patch to support uevent socket cpr
Andrey Zhadchenko (5):
vhost-blk: do not double close vhostfd
vhost-blk: change backend setup
vhost-blk: add read-only flag
vhost-blk: watch the device for resize events
vhost-blk: preserve the uevent socket across cpr-exec
hw/block/vhost-blk.c | 343 +++++++++++++++++++++++++++++-----
include/hw/virtio/vhost-blk.h | 10 +-
2 files changed, 307 insertions(+), 46 deletions(-)
--
2.43.5
next reply other threads:[~2026-09-04 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:21 Andrey Zhadchenko [this message]
2026-09-04 13:21 ` [QEMU HCI-8.0 PATCH v2 1/5] vhost-blk: do not double close vhostfd Andrey Zhadchenko
2026-09-04 15:33 ` Andrey Drobyshev
2026-09-04 13:21 ` [QEMU HCI-8.0 PATCH v2 2/5] vhost-blk: change backend setup Andrey Zhadchenko
2026-09-04 15:33 ` Andrey Drobyshev
2026-09-04 13:21 ` [QEMU HCI-8.0 PATCH v2 3/5] vhost-blk: add read-only flag Andrey Zhadchenko
2026-09-04 15:33 ` Andrey Drobyshev
2026-09-04 13:21 ` [QEMU HCI-8.0 PATCH v2 4/5] vhost-blk: watch the device for resize events Andrey Zhadchenko
2026-09-04 15:33 ` Andrey Drobyshev
2026-09-04 13:21 ` [QEMU HCI-8.0 PATCH v2 5/5] vhost-blk: preserve the uevent socket across cpr-exec Andrey Zhadchenko
2026-09-04 15:33 ` Andrey Drobyshev
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=20260904132155.180581-1-andrey.zhadchenko@virtuozzo.com \
--to=andrey.zhadchenko@virtuozzo.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=den@openvz.org \
--cc=svt-core@virtuozzo.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