diff options
| author | Steve Sistare <steven.sistare@oracle.com> | 2025-01-15 11:00:31 -0800 |
|---|---|---|
| committer | Fabiano Rosas <farosas@suse.de> | 2025-01-29 11:43:04 -0300 |
| commit | 6169f1193657d0ba630a2ce33cef639ae918bce4 (patch) | |
| tree | 33fd65ef73cb97e0b000bcb75e024b5a5d9226af /backends/hostmem-ram.c | |
| parent | 9fb40bb9621df9acb88a8128bee2e0f68631b245 (diff) | |
| download | qemu-6169f1193657d0ba630a2ce33cef639ae918bce4.zip qemu-6169f1193657d0ba630a2ce33cef639ae918bce4.tar.gz qemu-6169f1193657d0ba630a2ce33cef639ae918bce4.tar.bz2 | |
memory: add RAM_PRIVATE
Define the RAM_PRIVATE flag.
In RAMBlock creation functions, if MAP_SHARED is 0 in the flags parameter,
in a subsequent patch the implementation may still create a shared mapping
if other conditions require it. Callers who specifically want a private
mapping, eg for objects specified by the user, must pass RAM_PRIVATE.
After RAMBlock creation, MAP_SHARED in the block's flags indicates whether
the block is shared or private, and MAP_PRIVATE is omitted.
Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Link: https://lore.kernel.org/r/1736967650-129648-6-git-send-email-steven.sistare@oracle.com
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'backends/hostmem-ram.c')
| -rw-r--r-- | backends/hostmem-ram.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/backends/hostmem-ram.c b/backends/hostmem-ram.c index 39aac6b..868ae6c 100644 --- a/backends/hostmem-ram.c +++ b/backends/hostmem-ram.c @@ -28,7 +28,7 @@ ram_backend_memory_alloc(HostMemoryBackend *backend, Error **errp) } name = host_memory_backend_get_name(backend); - ram_flags = backend->share ? RAM_SHARED : 0; + ram_flags = backend->share ? RAM_SHARED : RAM_PRIVATE; ram_flags |= backend->reserve ? 0 : RAM_NORESERVE; ram_flags |= backend->guest_memfd ? RAM_GUEST_MEMFD : 0; return memory_region_init_ram_flags_nomigrate(&backend->mr, OBJECT(backend), |