From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, <qemu-block@nongnu.org>,
Hanna Reitz <hreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 0/4] block: update inserted/removed nodes from BlockRAMRegistrar
Date: Tue, 30 Sep 2025 16:45:51 -0400 [thread overview]
Message-ID: <20250930204555.162133-1-stefanha@redhat.com> (raw)
This patch series fixes a bug in BlockRAMRegistrar: it currently doesn't react
to block graph changes and newly inserted nodes lack RAMBlock information
needed to map I/O buffers. This is important for vdpa-blk devices because they
rely on the ability to map I/O buffers.
Stefan Hajnoczi (4):
block: add BdrvChildClass->propagate_attach/detach() callbacks
block: add blk_add_attach/detach_notifier() APIs
block: rename RAMBlockRegistrar->notifier field
block: update inserted/removed nodes from BlockRAMRegistrar
include/block/block_int-common.h | 11 ++
include/system/block-backend-global-state.h | 9 ++
include/system/block-ram-registrar.h | 4 +-
block.c | 56 +++++--
block/block-backend.c | 44 ++++++
block/block-ram-registrar.c | 75 ++++++++-
tests/unit/test-block-backend.c | 164 ++++++++++++++++++++
7 files changed, 344 insertions(+), 19 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-30 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 20:45 Stefan Hajnoczi [this message]
2025-09-30 20:45 ` [PATCH 1/4] block: add BdrvChildClass->propagate_attach/detach() callbacks Stefan Hajnoczi
2025-09-30 20:45 ` [PATCH 2/4] block: add blk_add_attach/detach_notifier() APIs Stefan Hajnoczi
2025-09-30 20:45 ` [PATCH 3/4] block: rename RAMBlockRegistrar->notifier field Stefan Hajnoczi
2025-09-30 20:45 ` [PATCH 4/4] block: update inserted/removed nodes from BlockRAMRegistrar Stefan Hajnoczi
2025-09-30 23:07 ` [PATCH 0/4] " Eric Blake
2025-10-01 15:00 ` 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=20250930204555.162133-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).