From: David Hildenbrand <david@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>,
Philippe Mathieu-Daude <philmd@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH V3 01/16] machine: anon-alloc option
Date: Mon, 4 Nov 2024 11:45:20 +0100 [thread overview]
Message-ID: <a1b51e4c-76db-41bf-b145-471869216589@redhat.com> (raw)
In-Reply-To: <78fa25f1-03dc-400c-a604-998c53e4fbce@redhat.com>
On 04.11.24 11:39, David Hildenbrand wrote:
> On 01.11.24 14:47, Steve Sistare wrote:
>> Allocate anonymous memory using mmap MAP_ANON or memfd_create depending
>> on the value of the anon-alloc machine property. This option applies to
>> memory allocated as a side effect of creating various devices. It does
>> not apply to memory-backend-objects, whether explicitly specified on
>> the command line, or implicitly created by the -m command line option.
>>
>> The memfd option is intended to support new migration modes, in which the
>> memory region can be transferred in place to a new QEMU process, by sending
>> the memfd file descriptor to the process. Memory contents are preserved,
>> and if the mode also transfers device descriptors, then pages that are
>> locked in memory for DMA remain locked. This behavior is a pre-requisite
>> for supporting vfio, vdpa, and iommufd devices with the new modes.
>
> A more portable, non-Linux specific variant of this will be using shm,
> similar to backends/hostmem-shm.c.
>
> Likely we should be using that instead of memfd, or try hiding the
> details. See below.
>
> [...]
>
>> @@ -69,6 +70,8 @@
>>
>> #include "qemu/pmem.h"
>>
>> +#include "qapi/qapi-types-migration.h"
>> +#include "migration/options.h"
>> #include "migration/vmstate.h"
>>
>> #include "qemu/range.h"
>> @@ -1849,6 +1852,35 @@ static void ram_block_add(RAMBlock *new_block, Error **errp)
>> qemu_mutex_unlock_ramlist();
>> return;
>> }
>> +
>> + } else if (current_machine->anon_alloc == ANON_ALLOC_OPTION_MEMFD &&
>> + !object_dynamic_cast(new_block->mr->parent_obj.parent,
>> + TYPE_MEMORY_BACKEND)) {
>
> This looks a bit and hackish, and I don't think ram_block_add() is the right
> place where this should be. It should likely happen in the caller.
>
> We already do have two ways of allocating "shared anonymous memory":
>
> (1) memory-backend-ram,share=on
> (2) memory-backend-shm
>
> (2) gives us an fd as it uses shm_open(), (1) doesn't give us an fd as it
> uses MAP_ANON|MAP_SHARED. (1) is really only a corner case use case [1].
>
> [there is also Linux specific memfd, which gives us more flexibility with
> hugetlb etc, but for the purpose here shm should likely be sufficient?]
>
> So why not make (1) behave like (2) and move that handling into
> qemu_ram_alloc_internal(), from where we can easily enable it using a
> new RMA_SHARED flag? So as a first step, something like:
>
> From 4b7b760c6e54cf05addca6728edc19adbec1588a Mon Sep 17 00:00:00 2001
> From: David Hildenbrand <david@redhat.com>
> Date: Mon, 4 Nov 2024 11:29:22 +0100
> Subject: [PATCH] tmp
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> backends/hostmem-shm.c | 56 ++++----------------------------
> system/physmem.c | 73 ++++++++++++++++++++++++++++++++++++++++--
> 2 files changed, 76 insertions(+), 53 deletions(-)
>
> diff --git a/backends/hostmem-shm.c b/backends/hostmem-shm.c
> index 374edc3db8..0f33b35e9c 100644
> --- a/backends/hostmem-shm.c
> +++ b/backends/hostmem-shm.c
> @@ -25,11 +25,8 @@ struct HostMemoryBackendShm {
> static bool
> shm_backend_memory_alloc(HostMemoryBackend *backend, Error **errp)
> {
> - g_autoptr(GString) shm_name = g_string_new(NULL);
> - g_autofree char *backend_name = NULL;
> + g_autofree char *name = NULL;
> uint32_t ram_flags;
> - int fd, oflag;
> - mode_t mode;
>
> if (!backend->size) {
> error_setg(errp, "can't create shm backend with size 0");
> @@ -41,54 +38,13 @@ shm_backend_memory_alloc(HostMemoryBackend *backend, Error **errp)
> return false;
> }
>
> - /*
> - * Let's use `mode = 0` because we don't want other processes to open our
> - * memory unless we share the file descriptor with them.
> - */
> - mode = 0;
> - oflag = O_RDWR | O_CREAT | O_EXCL;
> - backend_name = host_memory_backend_get_name(backend);
> -
> - /*
> - * Some operating systems allow creating anonymous POSIX shared memory
> - * objects (e.g. FreeBSD provides the SHM_ANON constant), but this is not
> - * defined by POSIX, so let's create a unique name.
> - *
> - * From Linux's shm_open(3) man-page:
> - * For portable use, a shared memory object should be identified
> - * by a name of the form /somename;"
> - */
> - g_string_printf(shm_name, "/qemu-" FMT_pid "-shm-%s", getpid(),
> - backend_name);
> -
> - fd = shm_open(shm_name->str, oflag, mode);
> - if (fd < 0) {
> - error_setg_errno(errp, errno,
> - "failed to create POSIX shared memory");
> - return false;
> - }
> -
> - /*
> - * We have the file descriptor, so we no longer need to expose the
> - * POSIX shared memory object. However it will remain allocated as long as
> - * there are file descriptors pointing to it.
> - */
> - shm_unlink(shm_name->str);
> -
> - if (ftruncate(fd, backend->size) == -1) {
> - error_setg_errno(errp, errno,
> - "failed to resize POSIX shared memory to %" PRIu64,
> - backend->size);
> - close(fd);
> - return false;
> - }
> -
> + /* Let's do the same as memory-backend-ram,share=on would do. */
> + name = host_memory_backend_get_name(backend);
> ram_flags = RAM_SHARED;
> ram_flags |= backend->reserve ? 0 : RAM_NORESERVE;
> -
> - return memory_region_init_ram_from_fd(&backend->mr, OBJECT(backend),
> - backend_name, backend->size,
> - ram_flags, fd, 0, errp);
> + return memory_region_init_ram_flags_nomigrate(&backend->mr, OBJECT(backend),
> + name, backend->size,
> + ram_flags, errp);
> }
>
> static void
> diff --git a/system/physmem.c b/system/physmem.c
> index dc1db3a384..4d331b3828 100644
> --- a/system/physmem.c
> +++ b/system/physmem.c
> @@ -2057,6 +2057,59 @@ RAMBlock *qemu_ram_alloc_from_file(ram_addr_t size, MemoryRegion *mr,
> }
> #endif
>
> +static int qemu_shm_alloc(size_t size, Error **errp)
> +{
> + g_autoptr(GString) shm_name = g_string_new(NULL);
> + int fd, oflag, cur_sequence;
> + static int sequence;
> + mode_t mode;
> +
> + cur_sequence = qatomic_fetch_inc(&sequence);
> +
> + /*
> + * Let's use `mode = 0` because we don't want other processes to open our
> + * memory unless we share the file descriptor with them.
> + */
> + mode = 0;
> + oflag = O_RDWR | O_CREAT | O_EXCL;
> +
> + /*
> + * Some operating systems allow creating anonymous POSIX shared memory
> + * objects (e.g. FreeBSD provides the SHM_ANON constant), but this is not
> + * defined by POSIX, so let's create a unique name.
> + *
> + * From Linux's shm_open(3) man-page:
> + * For portable use, a shared memory object should be identified
> + * by a name of the form /somename;"
> + */
> + g_string_printf(shm_name, "/qemu-" FMT_pid "-shm-%d", getpid(),
> + cur_sequence);
> +
> + fd = shm_open(shm_name->str, oflag, mode);
> + if (fd < 0) {
> + error_setg_errno(errp, errno,
> + "failed to create POSIX shared memory");
> + return false;
> + }
> +
> + /*
> + * We have the file descriptor, so we no longer need to expose the
> + * POSIX shared memory object. However it will remain allocated as long as
> + * there are file descriptors pointing to it.
> + */
> + shm_unlink(shm_name->str);
> +
> + if (ftruncate(fd, size) == -1) {
> + error_setg_errno(errp, errno,
> + "failed to resize POSIX shared memory to %" PRIu64,
> + size);
> + close(fd);
> + return false;
> + }
> +
> + return fd;
> +}
> +
> static
> RAMBlock *qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,
> void (*resized)(const char*,
> @@ -2084,12 +2137,26 @@ RAMBlock *qemu_ram_alloc_internal(ram_addr_t size, ram_addr_t max_size,
> new_block->used_length = size;
> new_block->max_length = max_size;
> assert(max_size >= size);
> - new_block->fd = -1;
> +
> new_block->guest_memfd = -1;
> new_block->page_size = qemu_real_host_page_size();
> - new_block->host = host;
> new_block->flags = ram_flags;
> - ram_block_add(new_block, &local_err);
> + new_block->host = host;
> +
> + if ((ram_flags & RAM_PREALLOC) || !(ram_flags & RAM_SHARED)) {
> + new_block->fd = -1;
> + } else {
> + /*
> + * We want anonymous shared memory, similar to MAP_SHARED|MAP_ANON; but
> + * some users want the fd. So let's allocate shm explicitly, which will
> + * give us the fd.
> + */
> + assert(!host);
> + new_block->fd = qemu_shm_alloc(new_block->max_length, &local_err);
Note: completely untested.
Likely a file_ram_alloc() call is missing here.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-11-04 10:46 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:47 [PATCH V3 00/16] Live update: cpr-transfer Steve Sistare
2024-11-01 13:47 ` [PATCH V3 01/16] machine: anon-alloc option Steve Sistare
2024-11-01 14:06 ` Peter Xu
2024-11-04 10:39 ` David Hildenbrand
2024-11-04 10:45 ` David Hildenbrand [this message]
2024-11-04 17:38 ` Steven Sistare
2024-11-04 19:51 ` David Hildenbrand
2024-11-04 20:14 ` Peter Xu
2024-11-04 20:17 ` David Hildenbrand
2024-11-04 20:41 ` Peter Xu
2024-11-04 20:15 ` David Hildenbrand
2024-11-04 20:56 ` Steven Sistare
2024-11-04 21:36 ` David Hildenbrand
2024-11-06 20:12 ` Steven Sistare
2024-11-06 20:41 ` Peter Xu
2024-11-06 20:59 ` Steven Sistare
2024-11-06 21:21 ` Peter Xu
2024-11-07 14:03 ` Steven Sistare
2024-11-07 13:05 ` David Hildenbrand
2024-11-07 14:04 ` Steven Sistare
2024-11-07 16:19 ` David Hildenbrand
2024-11-07 18:13 ` Steven Sistare
2024-11-07 16:32 ` Peter Xu
2024-11-07 16:38 ` David Hildenbrand
2024-11-07 17:48 ` Peter Xu
2024-11-07 13:23 ` David Hildenbrand
2024-11-07 16:02 ` Steven Sistare
2024-11-07 16:26 ` David Hildenbrand
2024-11-07 16:40 ` Steven Sistare
2024-11-08 11:31 ` David Hildenbrand
2024-11-08 13:43 ` Peter Xu
2024-11-08 14:14 ` Steven Sistare
2024-11-08 14:32 ` Peter Xu
2024-11-08 14:18 ` David Hildenbrand
2024-11-08 15:01 ` Peter Xu
2024-11-08 13:56 ` Steven Sistare
2024-11-08 14:20 ` David Hildenbrand
2024-11-08 14:37 ` Steven Sistare
2024-11-08 14:54 ` David Hildenbrand
2024-11-08 15:07 ` Peter Xu
2024-11-08 15:09 ` David Hildenbrand
2024-11-08 15:15 ` David Hildenbrand
2024-11-01 13:47 ` [PATCH V3 02/16] migration: cpr-state Steve Sistare
2024-11-13 20:36 ` Peter Xu
2024-11-01 13:47 ` [PATCH V3 03/16] physmem: preserve ram blocks for cpr Steve Sistare
2024-11-01 13:47 ` [PATCH V3 04/16] hostmem-memfd: preserve " Steve Sistare
2024-11-01 13:47 ` [PATCH V3 05/16] migration: SCM_RIGHTS for QEMUFile Steve Sistare
2024-11-13 20:54 ` Peter Xu
2024-11-14 18:34 ` Steven Sistare
2024-11-01 13:47 ` [PATCH V3 06/16] migration: VMSTATE_FD Steve Sistare
2024-11-13 20:55 ` Peter Xu
2024-11-01 13:47 ` [PATCH V3 07/16] migration: cpr-transfer save and load Steve Sistare
2024-11-01 13:47 ` [PATCH V3 08/16] migration: cpr-uri parameter Steve Sistare
2024-11-01 13:47 ` [PATCH V3 09/16] migration: cpr-uri option Steve Sistare
2024-11-01 13:47 ` [PATCH V3 10/16] migration: split qmp_migrate Steve Sistare
2024-11-13 21:11 ` Peter Xu
2024-11-14 18:33 ` Steven Sistare
2024-11-01 13:47 ` [PATCH V3 11/16] migration: cpr-transfer mode Steve Sistare
2024-11-13 21:58 ` Peter Xu
2024-11-14 18:36 ` Steven Sistare
2024-11-14 19:04 ` Peter Xu
2024-11-19 19:50 ` Steven Sistare
2024-11-19 20:16 ` Peter Xu
2024-11-19 20:32 ` Steven Sistare
2024-11-19 20:51 ` Peter Xu
2024-11-19 21:03 ` Steven Sistare
2024-11-19 21:29 ` Peter Xu
2024-11-19 21:41 ` Steven Sistare
2024-11-19 21:48 ` Peter Xu
2024-11-19 21:51 ` Steven Sistare
2024-11-20 9:38 ` Daniel P. Berrangé
2024-11-20 16:12 ` Steven Sistare
2024-11-20 16:26 ` Daniel P. Berrangé
2024-11-01 13:47 ` [PATCH V3 12/16] tests/migration-test: memory_backend Steve Sistare
2024-11-13 22:19 ` Fabiano Rosas
2024-11-01 13:47 ` [PATCH V3 13/16] tests/qtest: defer connection Steve Sistare
2024-11-13 22:36 ` Fabiano Rosas
2024-11-14 18:45 ` Steven Sistare
2024-11-13 22:53 ` Peter Xu
2024-11-14 18:31 ` Steven Sistare
2024-11-01 13:47 ` [PATCH V3 14/16] tests/migration-test: " Steve Sistare
2024-11-14 12:46 ` Fabiano Rosas
2024-11-01 13:47 ` [PATCH V3 15/16] migration-test: cpr-transfer Steve Sistare
2024-11-01 13:47 ` [PATCH V3 16/16] migration: cpr-transfer documentation Steve Sistare
2024-11-13 22:02 ` Peter Xu
2024-11-14 18:31 ` Steven Sistare
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=a1b51e4c-76db-41bf-b145-471869216589@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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 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).