From: Alex Fishman <afishman@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, sgarzare@redhat.com, farosas@suse.de,
lvivier@redhat.com, pbonzini@redhat.com,
Alex Fishman <afishman@redhat.com>
Subject: [PATCH v1 0/2] vhost: Handle vrings crossing virtio-mem slots
Date: Wed, 9 Sep 2026 15:59:21 +0300 [thread overview]
Message-ID: <20260909125923.75340-1-afishman@redhat.com> (raw)
Virtio-mem dynamic memslots are intentionally exposed as separate memory
regions. If a guest places a vring part across two adjacent slots, a later
memory update fails vhost ring verification because the complete ring part
is not contained in one vhost memory region.
Coalesce coherent adjacent sections only when a descriptor table,
available ring, or used ring crosses their boundary. Unrelated
unmergeable sections remain separate so they can still be updated
independently.
Patch 2 adds an end-to-end qtest reproducer using a fake vhost-user
backend and virtio-mem dynamic memslots. It also verifies that a newly
activated slot is not folded into the merge required by the crossing
vring.
Tested with the vhost-user/mem-slots/boundary qtest.
Buglink: https://redhat.atlassian.net/browse/RHEL-146583
Alex Fishman (2):
vhost: coalesce unmergeable sections across vring boundaries
tests/qtest: Add vhost-user memslot boundary test
hw/virtio/vhost.c | 72 ++++++-
tests/qtest/vhost-user-test.c | 395 +++++++++++++++++++++++++++++++++-
2 files changed, 452 insertions(+), 15 deletions(-)
base-commit: ff1d2d19d7e24893e2012d879f8e73077e17b9bd
--
2.52.0
next reply other threads:[~2026-09-09 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:59 Alex Fishman [this message]
2026-09-09 12:59 ` [PATCH v1 1/2] vhost: coalesce unmergeable sections across vring boundaries Alex Fishman
2026-09-09 13:31 ` Michael S. Tsirkin
2026-09-09 13:54 ` Alex Fishman
2026-09-09 15:24 ` Michael S. Tsirkin
2026-09-10 7:45 ` Michael S. Tsirkin
2026-09-09 12:59 ` [PATCH v1 2/2] tests/qtest: Add vhost-user memslot boundary test Alex Fishman
2026-09-09 13:01 ` [PATCH v1 0/2] vhost: Handle vrings crossing virtio-mem slots Michael S. Tsirkin
2026-09-09 13:13 ` Alex Fishman
2026-09-16 14:59 ` Stefan Hajnoczi
2026-09-16 15:10 ` Michael S. Tsirkin
2026-09-16 16:13 ` 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=20260909125923.75340-1-afishman@redhat.com \
--to=afishman@redhat.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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.