[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v1 08/15] memory-device: Track the actually used memslots in Devi
From: |
David Hildenbrand |
Subject: |
[PATCH v1 08/15] memory-device: Track the actually used memslots in DeviceMemoryState |
Date: |
Fri, 16 Jun 2023 11:26:47 +0200 |
Let's track how many memslots are currently getting used by memory
devices in the device memory region, and how many could be used at
maximum ("required"). "required - used" is the number of reserved memslots
that will get used in the future: we'll have to consider them when plugging
new vhost devices or new memory devices.
For now, the number of used and required memslots is always equal and
directly matches the number of memory devices. This is a preparation for
memory devices that want to dynamically consume memslots at runtime.
To track the number of used memslots, create a new address space for
our device memory and register a memory listener (add/remove) for that
address space.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
hw/mem/memory-device.c | 52 ++++++++++++++++++++++++++++++++++++++++++
include/hw/boards.h | 8 ++++++-
2 files changed, 59 insertions(+), 1 deletion(-)
diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
index a9dcc0c4ef..752258333b 100644
--- a/hw/mem/memory-device.c
+++ b/hw/mem/memory-device.c
@@ -406,6 +406,50 @@ uint64_t memory_device_get_region_size(const
MemoryDeviceState *md,
return memory_region_size(mr);
}
+static void memory_devices_region_mod(MemoryListener *listener,
+ MemoryRegionSection *mrs, bool add)
+{
+ DeviceMemoryState *dms = container_of(listener, DeviceMemoryState,
+ listener);
+
+ if (!memory_region_is_ram(mrs->mr)) {
+ warn_report("Unexpected memory region mapped into device memory
region.");
+ return;
+ }
+
+ /*
+ * The expectation is that each distinct RAM memory region section in
+ * our region for memory devices consumes exactly one memslot in KVM
+ * and in vhost. For vhost, this is true, except:
+ * * ROM memory regions don't consume a memslot. These get used very
+ * rarely for memory devices (R/O NVDIMMs).
+ * * Memslots without a fd (memory-backend-ram) don't necessarily
+ * consume a memslot. Such setups are quite rare and possibly bogus:
+ * the memory would be inaccessible by such vhost devices.
+ *
+ * So for vhost, in corner cases we might over-estimate the number of
+ * memslots that are currently used or that might still be reserved
+ * (required - used).
+ */
+ dms->used_memslots += add ? 1 : -1;
+
+ if (dms->used_memslots > dms->required_memslots) {
+ warn_report("Memory devices use more memory slots than indicated as
required.");
+ }
+}
+
+static void memory_devices_region_add(MemoryListener *listener,
+ MemoryRegionSection *mrs)
+{
+ return memory_devices_region_mod(listener, mrs, true);
+}
+
+static void memory_devices_region_del(MemoryListener *listener,
+ MemoryRegionSection *mrs)
+{
+ return memory_devices_region_mod(listener, mrs, false);
+}
+
void machine_memory_devices_init(MachineState *ms, hwaddr base, uint64_t size)
{
g_assert(size);
@@ -415,8 +459,16 @@ void machine_memory_devices_init(MachineState *ms, hwaddr
base, uint64_t size)
memory_region_init(&ms->device_memory->mr, OBJECT(ms), "device-memory",
size);
+ address_space_init(&ms->device_memory->as, &ms->device_memory->mr,
+ "device-memory");
memory_region_add_subregion(get_system_memory(), ms->device_memory->base,
&ms->device_memory->mr);
+
+ /* Track the number of memslots used by memory devices. */
+ ms->device_memory->listener.region_add = memory_devices_region_add;
+ ms->device_memory->listener.region_del = memory_devices_region_del;
+ memory_listener_register(&ms->device_memory->listener,
+ &ms->device_memory->as);
}
static const TypeInfo memory_device_info = {
diff --git a/include/hw/boards.h b/include/hw/boards.h
index a346b4ec4a..dcb6dc83ec 100644
--- a/include/hw/boards.h
+++ b/include/hw/boards.h
@@ -294,17 +294,23 @@ struct MachineClass {
* DeviceMemoryState:
* @base: address in guest physical address space where the memory
* address space for memory devices starts
- * @mr: address space container for memory devices
+ * @mr: memory region container for memory devices
+ * @as: address space for memory devices
+ * @listener: memory listener used to track used memslots in the addres space
* @dimm_size: the sum of plugged DIMMs' sizes
* @used_region_size: the part of @mr already used by memory devices
* @required_memslots: the number of memslots required by memory devices
+ * @used_memslots: the number of memslots currently used by memory devices
*/
typedef struct DeviceMemoryState {
hwaddr base;
MemoryRegion mr;
+ AddressSpace as;
+ MemoryListener listener;
uint64_t dimm_size;
uint64_t used_region_size;
unsigned int required_memslots;
+ unsigned int used_memslots;
} DeviceMemoryState;
/**
--
2.40.1
- [PATCH v1 00/15] virtio-mem: Expose device memory through multiple memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 01/15] memory-device: Track the required memslots in DeviceMemoryState, David Hildenbrand, 2023/06/16
- [PATCH v1 02/15] kvm: Add stub for kvm_get_max_memslots(), David Hildenbrand, 2023/06/16
- [PATCH v1 03/15] vhost: Add vhost_get_max_memslots(), David Hildenbrand, 2023/06/16
- [PATCH v1 04/15] memory-device, vhost: Add a memslot soft limit for memory devices, David Hildenbrand, 2023/06/16
- [PATCH v1 05/15] kvm: Return number of free memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 06/15] vhost: Return number of free memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 07/15] memory-device: Support memory devices that statically consume multiple memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 08/15] memory-device: Track the actually used memslots in DeviceMemoryState,
David Hildenbrand <=
- [PATCH v1 09/15] memory-device, vhost: Support memory devices that dynamically consume multiple memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 10/15] pc-dimm: Provide pc_dimm_get_free_slots() to query free ram slots, David Hildenbrand, 2023/06/16
- [PATCH v1 11/15] memory-device: Support memory-devices with auto-detection of the number of memslots, David Hildenbrand, 2023/06/16
- [PATCH v1 12/15] memory: Clarify mapping requirements for RamDiscardManager, David Hildenbrand, 2023/06/16
- [PATCH v1 13/15] virtio-mem: Expose device memory via multiple memslots if enabled, David Hildenbrand, 2023/06/16
- [PATCH v1 15/15] virtio-mem: Mark memslot alias memory regions unmergeable, David Hildenbrand, 2023/06/16
- [PATCH v1 14/15] memory, vhost: Allow for marking memory device memory regions unmergeable, David Hildenbrand, 2023/06/16