From: "Murilo Opsfelder Araújo" <muriloo@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Greg Kurz <groug@kaod.org>, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v1 08/13] util/mmap-alloc: Prepare for resizable mmaps
Date: Thu, 06 Feb 2020 09:31:40 -0300 [thread overview]
Message-ID: <6458667.Kg4MDSSyM0@kermit.br.ibm.com> (raw)
In-Reply-To: <5c261bcd-44df-b4a0-451d-83ec6ac48059@redhat.com>
Hello, David.
On Thursday, February 6, 2020 5:52:26 AM -03 David Hildenbrand wrote:
> On 06.02.20 00:00, Murilo Opsfelder Araújo wrote:
> > Hello, David.
> >
> > On Monday, February 3, 2020 3:31:20 PM -03 David Hildenbrand wrote:
> >> When shrinking a mmap we want to re-reserve the already populated area.
> >> When growing a memory region, we want to populate starting with a given
> >> fd_offset. Prepare by allowing to pass these parameters.
> >>
> >> Also, let's make sure we always process full pages, to avoid
> >> unmapping/remapping pages that are already in use when
> >> growing/shrinking. (existing callers seem to guarantee this, but that's
> >> not obvious)
> >>
> >> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> >> Cc: Greg Kurz <groug@kaod.org>
> >> Cc: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
> >> Cc: Eduardo Habkost <ehabkost@redhat.com>
> >> Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >> Signed-off-by: David Hildenbrand <david@redhat.com>
> >> ---
> >>
> >> util/mmap-alloc.c | 32 +++++++++++++++++++++-----------
> >> 1 file changed, 21 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/util/mmap-alloc.c b/util/mmap-alloc.c
> >> index f043ccb0ab..63ad6893b7 100644
> >> --- a/util/mmap-alloc.c
> >> +++ b/util/mmap-alloc.c
> >> @@ -83,12 +83,12 @@ size_t qemu_mempath_getpagesize(const char *mem_path)
> >>
> >> }
> >>
> >> /*
> >>
> >> - * Reserve a new memory region of the requested size to be used for
> >> mapping - * from the given fd (if any).
> >> + * Reserve a new memory region of the requested size or re-reserve parts
> >> + * of an existing region to be used for mapping from the given fd (if
> >> any). */
> >> -static void *mmap_reserve(size_t size, int fd)
> >> +static void *mmap_reserve(void *ptr, size_t size, int fd)
> >>
> >> {
> >>
> >> - int flags = MAP_PRIVATE;
> >> + int flags = MAP_PRIVATE | (ptr ? MAP_FIXED : 0);
> >>
> >> #if defined(__powerpc64__) && defined(__linux__)
> >>
> >> /*
> >>
> >> @@ -111,19 +111,23 @@ static void *mmap_reserve(size_t size, int fd)
> >>
> >> flags |= MAP_ANONYMOUS;
> >>
> >> #endif
> >>
> >> - return mmap(0, size, PROT_NONE, flags, fd, 0);
> >> + return mmap(ptr, size, PROT_NONE, flags, fd, 0);
> >>
> >> }
> >>
> >> /*
> >>
> >> * Populate memory in a reserved region from the given fd (if any).
> >> */
> >>
> >> -static void *mmap_populate(void *ptr, size_t size, int fd, bool shared,
> >> - bool is_pmem)
> >> +static void *mmap_populate(void *ptr, size_t size, int fd, size_t
> >> fd_offset, + bool shared, bool is_pmem)
> >>
> >> {
> >>
> >> int map_sync_flags = 0;
> >> int flags = MAP_FIXED;
> >> void *new_ptr;
> >>
> >> + if (fd == -1) {
> >> + fd_offset = 0;
> >> + }
> >> +
> >>
> >> flags |= fd == -1 ? MAP_ANONYMOUS : 0;
> >> flags |= shared ? MAP_SHARED : MAP_PRIVATE;
> >> if (shared && is_pmem) {
> >>
> >> @@ -131,7 +135,7 @@ static void *mmap_populate(void *ptr, size_t size,
> >> int
> >> fd, bool shared, }
> >>
> >> new_ptr = mmap(ptr, size, PROT_READ | PROT_WRITE, flags |
> >>
> >> map_sync_flags, - fd, 0);
> >> + fd, fd_offset);
> >>
> >> if (new_ptr == MAP_FAILED && map_sync_flags) {
> >>
> >> if (errno == ENOTSUP) {
> >>
> >> char *proc_link = g_strdup_printf("/proc/self/fd/%d", fd);
> >>
> >> @@ -153,7 +157,7 @@ static void *mmap_populate(void *ptr, size_t size,
> >> int
> >> fd, bool shared, * If mmap failed with MAP_SHARED_VALIDATE | MAP_SYNC, we
> >> will try * again without these flags to handle backwards compatibility.
> >> */
> >> - new_ptr = mmap(ptr, size, PROT_READ | PROT_WRITE, flags, fd, 0);
> >> + new_ptr = mmap(ptr, size, PROT_READ | PROT_WRITE, flags, fd,
> >> fd_offset); }
> >>
> >> return new_ptr;
> >>
> >> }
> >>
> >> @@ -178,13 +182,16 @@ void *qemu_ram_mmap(int fd,
> >>
> >> size_t offset, total;
> >> void *ptr, *guardptr;
> >>
> >> + /* we can only map whole pages */
> >> + size = QEMU_ALIGN_UP(size, pagesize);
> >> +
> >
> > Caller already rounds up size to block->page_size.
> >
> > Why this QEMU_ALIGN_UP is necessary?
>
> Thanks for having a look
>
> I guess you read the patch description, right? :)
>
> "(existing callers seem to guarantee this, but that's
> not obvious)"
>
> Do you prefer a g_assert(IS_ALIGNED()) instead?
I guess you mean QEMU_IS_ALIGNED(). But yes, I think we could just check
alignments here, so callers do the alignments first.
We could have, for example, a new helper function mmap_align(int size) that
returned size already aligned.
>
> Thanks!
--
Murilo
next prev parent reply other threads:[~2020-02-06 12:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 18:31 [PATCH v1 00/13] Ram blocks with resizable anonymous allocations under POSIX David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 01/13] util: vfio-helpers: Factor out and fix processing of existings ram blocks David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 02/13] exec: Factor out setting ram settings (madvise ...) into qemu_ram_apply_settings() David Hildenbrand
2020-02-06 11:42 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 03/13] exec: Reuse qemu_ram_apply_settings() in qemu_ram_remap() David Hildenbrand
2020-02-06 11:43 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 04/13] exec: Drop "shared" parameter from ram_block_add() David Hildenbrand
2020-02-06 11:44 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 05/13] util/mmap-alloc: Factor out calculation of pagesize to mmap_pagesize() David Hildenbrand
2020-02-05 19:37 ` Murilo Opsfelder Araújo
2020-02-06 11:46 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 06/13] util/mmap-alloc: Factor out reserving of a memory region to mmap_reserve() David Hildenbrand
2020-02-05 19:40 ` Murilo Opsfelder Araújo
2020-02-06 11:55 ` Richard Henderson
2020-02-06 13:16 ` David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 07/13] util/mmap-alloc: Factor out populating of memory to mmap_populate() David Hildenbrand
2020-02-05 19:56 ` Murilo Opsfelder Araújo
2020-02-06 9:26 ` David Hildenbrand
2020-02-06 11:59 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 08/13] util/mmap-alloc: Prepare for resizable mmaps David Hildenbrand
2020-02-05 23:00 ` Murilo Opsfelder Araújo
2020-02-06 8:52 ` David Hildenbrand
2020-02-06 12:31 ` Murilo Opsfelder Araújo [this message]
2020-02-06 13:16 ` David Hildenbrand
2020-02-06 15:13 ` David Hildenbrand
2020-02-06 12:02 ` Richard Henderson
2020-02-03 18:31 ` [PATCH v1 09/13] util/mmap-alloc: Implement " David Hildenbrand
2020-02-06 12:08 ` Richard Henderson
2020-02-06 13:22 ` David Hildenbrand
2020-02-06 15:27 ` David Hildenbrand
2020-02-07 0:29 ` Murilo Opsfelder Araújo
2020-02-10 9:39 ` David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 10/13] numa: Introduce ram_block_notify_resized() and ram_block_notifiers_support_resize() David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 11/13] util: vfio-helpers: Implement ram_block_resized() David Hildenbrand
2020-02-10 13:41 ` David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 12/13] util: oslib: Resizable anonymous allocations under POSIX David Hildenbrand
2020-02-03 18:31 ` [PATCH v1 13/13] exec: Ram blocks with resizable " David Hildenbrand
2020-02-10 10:12 ` David Hildenbrand
2020-02-06 9:27 ` [PATCH v1 00/13] " Michael S. Tsirkin
2020-02-06 9:45 ` David Hildenbrand
2020-02-06 20:11 ` Dr. David Alan Gilbert
2020-02-06 20:31 ` David Hildenbrand
2020-02-07 15:28 ` Dr. David Alan Gilbert
2020-02-10 9:47 ` David Hildenbrand
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=6458667.Kg4MDSSyM0@kermit.br.ibm.com \
--to=muriloo@linux.ibm.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).