From: Yi Zhang <yi.z.zhang@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: xiaoguangrong.eric@gmail.com, stefanha@redhat.com,
pbonzini@redhat.com, pagupta@redhat.com,
yu.c.zhang@linux.intel.com, richardw.yang@linux.intel.com,
ehabkost@redhat.com, qemu-devel@nongnu.org, imammedo@redhat.com,
dan.j.williams@intel.com
Subject: Re: [Qemu-devel] [PATCH V10 2/4] util/mmap-alloc: support MAP_SYNC in qemu_ram_mmap()
Date: Thu, 24 Jan 2019 22:15:24 +0800 [thread overview]
Message-ID: <20190124141524.GB9821@tiger-server> (raw)
In-Reply-To: <20190123100252-mutt-send-email-mst@kernel.org>
On 2019-01-23 at 10:04:01 -0500, Michael S. Tsirkin wrote:
> On Wed, Jan 23, 2019 at 10:59:45AM +0800, Zhang, Yi wrote:
> > From: Zhang Yi <yi.z.zhang@linux.intel.com>
> >
> > When a file supporting DAX is used as vNVDIMM backend, mmap it with
> > MAP_SYNC flag in addition which can ensure file system metadata
> > synced in each guest writes to the backend file, without other QEMU
> > actions (e.g., periodic fsync() by QEMU).
> >
> > Current, We have below different possible use cases:
> >
> > 1. pmem=on is set, shared=on is set, MAP_SYNC supported:
> > a: backend is a dax supporting file.
> > - MAP_SYNC will active.
> > b: backend is not a dax supporting file.
> > - mmap will result in an EOPNOTSUPP error.
> >
> > 2. The rest of cases:
> > - we will never pass the MAP_SYNC to mmap2
> >
> > Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> > Signed-off-by: Zhang Yi <yi.z.zhang@linux.intel.com>
> > ---
> > include/qemu/mmap-alloc.h | 1 +
> > include/qemu/osdep.h | 21 +++++++++++++++++++++
> > util/mmap-alloc.c | 7 ++++++-
> > 3 files changed, 28 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/qemu/mmap-alloc.h b/include/qemu/mmap-alloc.h
> > index 6fe6ed4..a95d91c 100644
> > --- a/include/qemu/mmap-alloc.h
> > +++ b/include/qemu/mmap-alloc.h
> > @@ -18,6 +18,7 @@ size_t qemu_mempath_getpagesize(const char *mem_path);
> > * @flags: specifies additional properties of the mapping, which can be one or
> > * bit-or of following values
> > * - RAM_SHARED: mmap with MAP_SHARED flag
> > + * - RAM_PMEM: mmap with MAP_SYNC flag
> > * Other bits are ignored.
> > *
> > * Return:
> > diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> > index 457d24e..3bcf155 100644
> > --- a/include/qemu/osdep.h
> > +++ b/include/qemu/osdep.h
> > @@ -419,6 +419,27 @@ void qemu_anon_ram_free(void *ptr, size_t size);
> > # define QEMU_VMALLOC_ALIGN getpagesize()
> > #endif
> >
> > +/*
> > + * MAP_SHARED_VALIDATE and MAP_SYNC are introduced in Linux kernel
> > + * 4.15, so they may not be defined when compiling on older kernels.
> > + */
>
>
> I commented on this part in v7. That's a wrong way to handle
> compatibility.
I'm a little confused that, you point me that should use
#include <linux/mman.h>
here in v9, so what is best way to handle compatibility?
modify the update-linux-headers.sh and copy the mman.h to
standard-headers/linux/?
and #incldue standard-headers/linux/mman.h ?
but it still need fix the compatibility. if the MAP_SYNC not defined in
the old kernel. Right?
forgive me my poor understandings, I'm pazzled.
>
> > +#ifdef CONFIG_LINUX
> > +
> > +#include <linux/mman.h>
> > +
> > +#ifndef MAP_SYNC
> > +#define MAP_SYNC 0x0
> > +#endif
> > +
> > +#ifndef MAP_SHARED_VALIDATE
> > +#define MAP_SHARED_VALIDATE 0x0
> > +#endif
> > +
>
>
>
>
> > +#else /* !CONFIG_LINUX */
> > +#define MAP_SYNC 0x0
> > +#define MAP_SHARED_VALIDATE 0x0
> > +#endif /* CONFIG_LINUX */
> > +
> > #ifdef CONFIG_POSIX
> > struct qemu_signalfd_siginfo {
> > uint32_t ssi_signo; /* Signal number */
> > diff --git a/util/mmap-alloc.c b/util/mmap-alloc.c
> > index 8f0a740..a4ce9b5 100644
> > --- a/util/mmap-alloc.c
> > +++ b/util/mmap-alloc.c
> > @@ -99,6 +99,8 @@ void *qemu_ram_mmap(int fd, size_t size, size_t align, uint32_t flags)
> > void *ptr = mmap(0, total, PROT_NONE, MAP_ANONYMOUS | MAP_PRIVATE, -1, 0);
> > #endif
> > bool shared = flags & RAM_SHARED;
> > + bool is_pmem = flags & RAM_PMEM;
> > + int mmap_xflags = 0;
> > size_t offset;
> > void *ptr1;
> >
> > @@ -109,12 +111,15 @@ void *qemu_ram_mmap(int fd, size_t size, size_t align, uint32_t flags)
> > assert(is_power_of_2(align));
> > /* Always align to host page size */
> > assert(align >= getpagesize());
> > + if (shared && is_pmem) {
> > + mmap_xflags |= (MAP_SYNC | MAP_SHARED_VALIDATE);
> > + }
> >
> > offset = QEMU_ALIGN_UP((uintptr_t)ptr, align) - (uintptr_t)ptr;
> > ptr1 = mmap(ptr + offset, size, PROT_READ | PROT_WRITE,
> > MAP_FIXED |
> > (fd == -1 ? MAP_ANONYMOUS : 0) |
> > - (shared ? MAP_SHARED : MAP_PRIVATE),
> > + (shared ? MAP_SHARED : MAP_PRIVATE) | mmap_xflags,
> > fd, 0);
> > if (ptr1 == MAP_FAILED) {
> > munmap(ptr, total);
> > --
> > 2.7.4
next prev parent reply other threads:[~2019-01-24 5:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 2:59 [Qemu-devel] [PATCH V10 0/4] support MAP_SYNC for memory-backend-file Zhang, Yi
2019-01-23 2:59 ` [Qemu-devel] [PATCH V10 1/4] util/mmap-alloc: switch 'shared' to 'flags' parameter Zhang, Yi
2019-01-23 15:01 ` Michael S. Tsirkin
2019-01-23 2:59 ` [Qemu-devel] [PATCH V10 2/4] util/mmap-alloc: support MAP_SYNC in qemu_ram_mmap() Zhang, Yi
2019-01-23 15:04 ` Michael S. Tsirkin
2019-01-24 14:15 ` Yi Zhang [this message]
2019-01-24 13:39 ` Michael S. Tsirkin
2019-01-23 2:59 ` [Qemu-devel] [PATCH V10 3/4] hostmem: add more information in error messages Zhang, Yi
2019-01-23 3:00 ` [Qemu-devel] [PATCH V10 4/4] docs: Added MAP_SYNC documentation Zhang, Yi
2019-01-23 14:50 ` Eduardo Habkost
2019-01-24 11:21 ` Yi Zhang
2019-01-24 16:59 ` Eduardo Habkost
2019-01-24 17:45 ` Michael S. Tsirkin
2019-01-24 18:28 ` Eduardo Habkost
2019-01-24 19:05 ` Michael S. Tsirkin
2019-01-24 19:14 ` Eduardo Habkost
2019-01-25 3:08 ` Michael S. Tsirkin
2019-01-25 3:26 ` Eduardo Habkost
2019-01-25 20:01 ` Michael S. Tsirkin
2019-01-25 20:03 ` Michael S. Tsirkin
2019-01-25 11:19 ` Yi Zhang
2019-01-23 3:01 ` [Qemu-devel] [PATCH V10 0/4] support MAP_SYNC for memory-backend-file Michael S. Tsirkin
2019-01-23 3:10 ` Yi Zhang
2019-01-23 3:53 ` Michael S. Tsirkin
2019-01-23 15:45 ` Yi Zhang
2019-01-23 4:02 ` Michael S. Tsirkin
2019-01-23 15:57 ` Yi Zhang
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=20190124141524.GB9821@tiger-server \
--to=yi.z.zhang@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=yu.c.zhang@linux.intel.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).