[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v6 03/13] numa: call ->ram_block_removed() in ram_block_notifer_r
From: |
Stefan Hajnoczi |
Subject: |
[PATCH v6 03/13] numa: call ->ram_block_removed() in ram_block_notifer_remove() |
Date: |
Thu, 6 Oct 2022 17:34:57 -0400 |
When a RAMBlockNotifier is added, ->ram_block_added() is called with all
existing RAMBlocks. There is no equivalent ->ram_block_removed() call
when a RAMBlockNotifier is removed.
The util/vfio-helpers.c code (the sole user of RAMBlockNotifier) is fine
with this asymmetry because it does not rely on RAMBlockNotifier for
cleanup. It walks its internal list of DMA mappings and unmaps them by
itself.
Future users of RAMBlockNotifier may not have an internal data structure
that records added RAMBlocks so they will need ->ram_block_removed()
callbacks.
This patch makes ram_block_notifier_remove() symmetric with respect to
callbacks. Now util/vfio-helpers.c needs to unmap remaining DMA mappings
after ram_block_notifier_remove() has been called. This is necessary
since users like block/nvme.c may create additional DMA mappings that do
not originate from the RAMBlockNotifier.
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/core/numa.c | 17 +++++++++++++++++
util/vfio-helpers.c | 5 ++++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/hw/core/numa.c b/hw/core/numa.c
index 26d8e5f616..31e6fe1caa 100644
--- a/hw/core/numa.c
+++ b/hw/core/numa.c
@@ -822,6 +822,19 @@ static int ram_block_notify_add_single(RAMBlock *rb, void
*opaque)
return 0;
}
+static int ram_block_notify_remove_single(RAMBlock *rb, void *opaque)
+{
+ const ram_addr_t max_size = qemu_ram_get_max_length(rb);
+ const ram_addr_t size = qemu_ram_get_used_length(rb);
+ void *host = qemu_ram_get_host_addr(rb);
+ RAMBlockNotifier *notifier = opaque;
+
+ if (host) {
+ notifier->ram_block_removed(notifier, host, size, max_size);
+ }
+ return 0;
+}
+
void ram_block_notifier_add(RAMBlockNotifier *n)
{
QLIST_INSERT_HEAD(&ram_list.ramblock_notifiers, n, next);
@@ -835,6 +848,10 @@ void ram_block_notifier_add(RAMBlockNotifier *n)
void ram_block_notifier_remove(RAMBlockNotifier *n)
{
QLIST_REMOVE(n, next);
+
+ if (n->ram_block_removed) {
+ qemu_ram_foreach_block(ram_block_notify_remove_single, n);
+ }
}
void ram_block_notify_add(void *host, size_t size, size_t max_size)
diff --git a/util/vfio-helpers.c b/util/vfio-helpers.c
index 5ba01177bf..0d1520caac 100644
--- a/util/vfio-helpers.c
+++ b/util/vfio-helpers.c
@@ -847,10 +847,13 @@ void qemu_vfio_close(QEMUVFIOState *s)
if (!s) {
return;
}
+
+ ram_block_notifier_remove(&s->ram_notifier);
+
for (i = 0; i < s->nr_mappings; ++i) {
qemu_vfio_undo_mapping(s, &s->mappings[i], NULL);
}
- ram_block_notifier_remove(&s->ram_notifier);
+
g_free(s->usable_iova_ranges);
s->nb_iova_ranges = 0;
qemu_vfio_reset(s);
--
2.37.3
- [PATCH v6 00/13] blkio: add libblkio BlockDriver, Stefan Hajnoczi, 2022/10/06
- [PATCH v6 01/13] coroutine: add flag to re-queue at front of CoQueue, Stefan Hajnoczi, 2022/10/06
- [PATCH v6 02/13] blkio: add libblkio block driver, Stefan Hajnoczi, 2022/10/06
- [PATCH v6 04/13] block: pass size to bdrv_unregister_buf(), Stefan Hajnoczi, 2022/10/06
- [PATCH v6 03/13] numa: call ->ram_block_removed() in ram_block_notifer_remove(),
Stefan Hajnoczi <=
- [PATCH v6 07/13] block: return errors from bdrv_register_buf(), Stefan Hajnoczi, 2022/10/06
- [PATCH v6 09/13] block: add BlockRAMRegistrar, Stefan Hajnoczi, 2022/10/06
- [PATCH v6 05/13] block: use BdrvRequestFlags type for supported flag fields, Stefan Hajnoczi, 2022/10/06
- [PATCH v6 11/13] stubs: add qemu_ram_block_from_host() and qemu_ram_get_fd(), Stefan Hajnoczi, 2022/10/06
- [PATCH v6 08/13] numa: use QLIST_FOREACH_SAFE() for RAM block notifiers, Stefan Hajnoczi, 2022/10/06