From: Yi Zhang <yi.z.zhang@linux.intel.com>
To: xiaoguangrong.eric@gmail.com, dan.j.williams@intel.com,
stefanha@redhat.com, pbonzini@redhat.com,
yu.c.zhang@linux.intel.com
Cc: mst@redhat.com, qemu-devel@nongnu.org, imammedo@redhat.com,
ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH V5_resend 0/7] nvdimm: support MAP_SYNC for memory-backend-file
Date: Mon, 26 Nov 2018 11:00:51 +0800 [thread overview]
Message-ID: <20181126030050.GA51343@tiger-server> (raw)
In-Reply-To: <cover.1542699775.git.yi.z.zhang@linux.intel.com>
Ping for any review/comments
Thanks
Yi
On 2018-11-20 at 15:47:58 +0800, Zhang Yi wrote:
> Linux 4.15 introduces a new mmap flag MAP_SYNC, which can be used to
> guarantee the write persistence to mmap'ed files supporting DAX (e.g.,
> files on ext4/xfs file system mounted with '-o dax').
>
> A description of MAP_SYNC and MAP_SHARED_VALIDATE can be found at
> https://patchwork.kernel.org/patch/10028151/
>
> In order to make sure that the file metadata is in sync after a fault
> while we are writing a shared DAX supporting backend files, this
> patch-set enables QEMU to use MAP_SYNC flag for memory-backend-dax-file.
>
> As the DAX vs DMA truncated issue was solved, we refined the code and
> send out this feature for the v5 version.
>
> A new auto on/off option 'sync' is added to memory-backend-file:
> - on: try to pass MAP_SYNC to mmap(2); if MAP_SYNC is not supported or
> 'share=off', QEMU will abort
> - off: never pass MAP_SYNC to mmap(2)
> - auto (default): if MAP_SYNC is supported and 'share=on', work as if
> 'sync=on'; otherwise, work as if 'sync=off'
Changes in v5:
* Add patch 1 to fix a memory leak issue.
* Refine the patch 4-6
* Remove the patch 3 as we already change the parameter from "shared" to
"flags"
Changes in v4:
* Add patch 1-3 to switch some functions to a single 'flags'
parameters. (Michael S. Tsirkin)
* v3 patch 1-3 become v4 patch 4-6.
* Patch 4: move definitions of MAP_SYNC and MAP_SHARED_VALIDATE to a
new header file under include/standard-headers/linux/. (Michael S. Tsirkin)
* Patch 6: refine the description of the 'sync' option. (Michael S. Tsirkin)
Changes in v3:
* Patch 1: add MAP_SHARED_VALIDATE in both sync=on and sync=auto
cases, and add back the retry mechanism. MAP_SYNC will be ignored
by Linux kernel 4.15 if MAP_SHARED_VALIDATE is missed.
* Patch 1: define MAP_SYNC and MAP_SHARED_VALIDATE as 0 on non-Linux
platforms in order to make qemu_ram_mmap() compile on those platforms.
* Patch 2&3: include more information in error messages of
memory-backend in hope to help user to identify the error.
(Dr. David Alan Gilbert)
* Patch 3: fix typo in the commit message. (Dr. David Alan Gilbert)
Changes in v2:
* Add 'sync' option to control the use of MAP_SYNC. (Eduardo Habkost)
* Remove the unnecessary set of MAP_SHARED_VALIDATE in some cases and
the retry mechanism in qemu_ram_mmap(). (Michael S. Tsirkin)
* Move OS dependent definitions of MAP_SYNC and MAP_SHARED_VALIDATE
to osdep.h. (Michael S. Tsirkin)
>
> Zhang Yi (7):
> numa: Fixed the memory leak of numa error message
> util/mmap-alloc: switch qemu_ram_mmap() to 'flags' parameter
> exec: switch qemu_ram_alloc_from_{file, fd} to the 'flags' parameter
> util/mmap-alloc: support MAP_SYNC in qemu_ram_mmap()
> util/mmap-alloc: Switch the RAM_SYNC flags to OnOffAuto
> hostmem: add more information in error messages
> hostmem-file: add 'sync' option
>
> backends/hostmem-file.c | 45 +++++++++++++++++++++++++++++++++--
> backends/hostmem.c | 8 ++++---
> docs/nvdimm.txt | 20 +++++++++++++++-
> exec.c | 9 +++----
> include/exec/memory.h | 18 ++++++++++++++
> include/exec/ram_addr.h | 1 +
> include/qemu/mmap-alloc.h | 20 +++++++++++++++-
> include/standard-headers/linux/mman.h | 44 ++++++++++++++++++++++++++++++++++
> numa.c | 1 +
> qemu-options.hx | 22 ++++++++++++++++-
> util/mmap-alloc.c | 26 ++++++++++++++++----
> util/oslib-posix.c | 4 +++-
> 12 files changed, 200 insertions(+), 18 deletions(-)
> create mode 100644 include/standard-headers/linux/mman.h
>
> --
> 2.7.4
>
prev parent reply other threads:[~2018-11-26 3:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 7:47 [Qemu-devel] [PATCH V5_resend 0/7] nvdimm: support MAP_SYNC for memory-backend-file Zhang Yi
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 1/7] numa: Fixed the memory leak of numa error message Zhang Yi
2018-11-26 13:10 ` Igor Mammedov
2018-11-29 8:41 ` Pankaj Gupta
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 2/7] util/mmap-alloc: switch qemu_ram_mmap() to 'flags' parameter Zhang Yi
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 3/7] exec: switch qemu_ram_alloc_from_{file, fd} to the " Zhang Yi
2018-11-29 9:11 ` Pankaj Gupta
2018-12-04 7:28 ` Yi Zhang
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 4/7] util/mmap-alloc: support MAP_SYNC in qemu_ram_mmap() Zhang Yi
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 5/7] util/mmap-alloc: Switch the RAM_SYNC flags to OnOffAuto Zhang Yi
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 6/7] hostmem: add more information in error messages Zhang Yi
2018-11-20 7:48 ` [Qemu-devel] [PATCH V5_resend 7/7] hostmem-file: add 'sync' option Zhang Yi
2018-11-26 8:46 ` Pankaj Gupta
2018-12-04 7:32 ` Yi Zhang
2018-11-26 3:00 ` Yi Zhang [this message]
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=20181126030050.GA51343@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=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).