From: David Hildenbrand <david@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <mapfelba@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Peter Xu <peterx@redhat.com>, Greg Kurz <groug@kaod.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5 04/14] softmmu/memory: Pass ram_flags to qemu_ram_alloc_from_fd()
Date: Tue, 20 Apr 2021 12:36:04 +0200 [thread overview]
Message-ID: <063387fa-0123-5260-dfb5-caf482dfcd05@redhat.com> (raw)
In-Reply-To: <6ab168bd-113c-6fcb-658a-70f71aca4ab0@redhat.com>
On 20.04.21 12:18, Philippe Mathieu-Daudé wrote:
> Hi David,
>
> On 4/20/21 11:52 AM, Philippe Mathieu-Daudé wrote:
>> On 4/13/21 11:14 AM, David Hildenbrand wrote:
>>> Let's pass in ram flags just like we do with qemu_ram_alloc_from_file(),
>>> to clean up and prepare for more flags.
>>>
>>> Simplify the documentation of passed ram flags: Looking at our
>>> documentation of RAM_SHARED and RAM_PMEM is sufficient, no need to be
>>> repetitive.
>>>
>>> Reviewed-by: Peter Xu <peterx@redhat.com>
>>> Signed-off-by: David Hildenbrand <david@redhat.com>
>>> ---
>>> backends/hostmem-memfd.c | 7 ++++---
>>> hw/misc/ivshmem.c | 5 ++---
>>> include/exec/memory.h | 9 +++------
>>> include/exec/ram_addr.h | 6 +-----
>>> softmmu/memory.c | 7 +++----
>>> 5 files changed, 13 insertions(+), 21 deletions(-)
>>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>
>
> Actually it would be clearer to define the 0 value, maybe:
>
> #define RAM_NOFLAG (0 << 0)
>
This will also turn some code into
ram_flags = backend->share ? RAM_SHARED : RAM_NOFLAG;
ram_flags |= backend->reserve ? RAM_NOFLAG : RAM_NORESERVE;
Looking at other flag users, I barely see any such usage.
XKB_CONTEXT_NO_FLAGS, ALLOC_NO_FLAGS, and MEM_AFFINITY_NOFLAGS seem to
be the only ones. That's why I tend to not do it unless there are strong
opinions.
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-04-20 10:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 9:14 [PATCH v5 00/14] RAM_NORESERVE, MAP_NORESERVE and hostmem "reserve" property David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 01/14] util/mmap-alloc: Factor out calculation of the pagesize for the guard page David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 02/14] util/mmap-alloc: Factor out reserving of a memory region to mmap_reserve() David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 03/14] util/mmap-alloc: Factor out activating of memory to mmap_activate() David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 04/14] softmmu/memory: Pass ram_flags to qemu_ram_alloc_from_fd() David Hildenbrand
2021-04-20 9:52 ` Philippe Mathieu-Daudé
2021-04-20 10:18 ` Philippe Mathieu-Daudé
2021-04-20 10:36 ` David Hildenbrand [this message]
2021-04-20 10:45 ` Philippe Mathieu-Daudé
2021-04-20 11:03 ` David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 05/14] softmmu/memory: Pass ram_flags to memory_region_init_ram_shared_nomigrate() David Hildenbrand
2021-04-20 10:20 ` Philippe Mathieu-Daudé
2021-04-20 10:27 ` David Hildenbrand
2021-04-20 10:40 ` Philippe Mathieu-Daudé
2021-04-20 11:10 ` David Hildenbrand
2021-04-20 11:43 ` David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 06/14] util/mmap-alloc: Pass flags instead of separate bools to qemu_ram_mmap() David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 07/14] memory: Introduce RAM_NORESERVE and wire it up in qemu_ram_mmap() David Hildenbrand
2021-04-20 10:25 ` Philippe Mathieu-Daudé
2021-04-13 9:14 ` [PATCH v5 08/14] util/mmap-alloc: Support RAM_NORESERVE via MAP_NORESERVE under Linux David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 09/14] hostmem: Wire up RAM_NORESERVE via "reserve" property David Hildenbrand
2021-04-13 9:14 ` [PATCH v5 10/14] qmp: Clarify memory backend properties returned via query-memdev David Hildenbrand
2021-04-20 10:27 ` Philippe Mathieu-Daudé
2021-04-13 9:14 ` [PATCH v5 11/14] qmp: Include "share" property of memory backends David Hildenbrand
2021-04-20 10:28 ` Philippe Mathieu-Daudé
2021-04-13 9:14 ` [PATCH v5 12/14] hmp: Print "share" property of memory backends with "info memdev" David Hildenbrand
2021-04-14 18:56 ` Dr. David Alan Gilbert
2021-04-20 10:46 ` Philippe Mathieu-Daudé
2021-04-13 9:14 ` [PATCH v5 13/14] qmp: Include "reserve" property of memory backends David Hildenbrand
2021-04-20 10:47 ` Philippe Mathieu-Daudé
2021-04-13 9:14 ` [PATCH v5 14/14] hmp: Print "reserve" property of memory backends with "info memdev" David Hildenbrand
2021-04-20 10:49 ` Philippe Mathieu-Daudé
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=063387fa-0123-5260-dfb5-caf482dfcd05@redhat.com \
--to=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=mapfelba@redhat.com \
--cc=mst@redhat.com \
--cc=muriloo@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.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).