qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: junyan.he@gmx.com, ehabkost@redhat.com, quintela@redhat.com,
	rth@twiddle.net, crosthwaite.peter@gmail.com,
	qemu-devel@nongnu.org, dgilbert@redhat.com,
	Junyan He <junyan.he@intel.com>,
	stefanha@redhat.com, imammedo@redhat.com, pbonzini@redhat.com,
	yi.z.zhang@intel.com, xiaoguangrong.eric@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/7 V11] nvdimm: guarantee persistence of QEMU writes to persistent memory
Date: Fri, 27 Jul 2018 16:06:23 +0300	[thread overview]
Message-ID: <20180727160529-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180727124917.GC28555@stefanha-x1.localdomain>

On Fri, Jul 27, 2018 at 01:49:17PM +0100, Stefan Hajnoczi wrote:
> On Wed, Jul 18, 2018 at 03:47:56PM +0800, junyan.he@gmx.com wrote:
> > From: Junyan He <junyan.he@intel.com>
> > 
> > QEMU writes to vNVDIMM backends in the vNVDIMM label emulation and live migration.
> > If the backend is on the persistent memory, QEMU needs to take proper operations to
> > ensure its writes persistent on the persistent memory. Otherwise, a host power failure
> > may result in the loss the guest data on the persistent memory.
> 
> Ping Michael.  Can this go through your tree?

OK but do you really think it's appropriate in this release cycle?
If not pls repost after the release including the acks.

> > 
> > This patch series is based on Marcel's patch "mem: add share parameter to memory-backend-ram" [1]
> > because of the changes in patch 1.
> > [1] https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg03858.html
> > 
> > Previous versions of this patch series can be found at: 
> > v10: https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg03433.html
> > v9: https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg02361.html
> > v8: https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg02279.html
> > v7: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg02997.html
> > v6: https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg00061.html
> > v5: https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg02258.html
> > V4: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg06993.html
> > v3: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg04365.html
> > v2: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg01579.html
> > v1: https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg05040.html
> > 
> > Changes in v11:
> > * (Patch 2) Modify the ram_flags parameter to 32bits, the same size as it in RAMBlock
> > * (Patch 5 and Patch 7) Delete pmem_xxx stub functions in stubs/pmem.c. Use inline
> > functions with assert to replace them, because we never come there when pmem is enabled
> > but lack of libpmem support.
> > 
> > Changes in v10:
> > * (Patch 4) Fix a nit in nvdimm docs about pmem option usage in command line 
> > The v10 patch set is all reviewed by Igor Mammedov <imammedo@redhat.com>
> > 
> > Changes in v9:
> > * (Patch 3 and Patch 4) Reorder these two patches to make logic right.
> > Firstly add libpmem support, and then we can use libpmem's configure
> > check result. Also fix some typo and grammar issues in these two patches.
> > 
> > Changs in v8: 
> > * (Patch 3) Report a error when user set 'pmem' to file-backend, while
> > the qemu is lack of libpmem support. In this case, we can not ensure
> > the persistence of the file-backend, so we choose to fail the build
> > rather than contine and make the thing more confused.
> > 
> > Changes in v7: 
> > The v6 patch set has already reviewed by Stefan Hajnoczi <stefanha@redhat.com>
> > No logic change in this v7 version, just:
> > * Spelling check and some document words refined.
> > * Rebase to "ram is migratable" patch set.
> > 
> > Changes in v6: 
> > * (Patch 1) Expose all ram block flags rather than redefine the flags.
> > * (Patch 4) Use pkg-config rather the hard check when configure. 
> > * (Patch 7) Sync and flush all the pmem data when migration completes,
> > rather than sync pages one by one in previous version.
> > 
> > Changes in v5: 
> > * (Patch 9) Add post copy check and output some messages for nvdimm.
> > 
> > Changes in v4: 
> > * (Patch 2) Fix compilation errors found by patchew.
> > 
> > Changes in v3:
> > * (Patch 5) Add a is_pmem flag to ram_handle_compressed() and handle
> > PMEM writes in it, so we don't need the _common function.
> > * (Patch 6) Expose qemu_get_buffer_common so we can remove the
> > unnecessary qemu_get_buffer_to_pmem wrapper.
> > * (Patch 8) Add a is_pmem flag to xbzrle_decode_buffer() and handle
> > PMEM writes in it, so we can remove the unnecessary
> > xbzrle_decode_buffer_{common, to_pmem}.
> > * Move libpmem stubs to stubs/pmem.c and fix the compilation failures
> > of test-{xbzrle,vmstate}.c.
> > 
> > Changes in v2:
> > * (Patch 1) Use a flags parameter in file ram allocation functions.
> > * (Patch 2) Add a new option 'pmem' to hostmem-file.
> > * (Patch 3) Use libpmem to operate on the persistent memory, rather
> > than re-implementing those operations in QEMU.
> > * (Patch 5-8) Consider the write persistence in the migration path.
> > 
> > 
> > Junyan:
> > [1/7] memory, exec: Expose all memory block related flags.
> > [6/7] migration/ram: Add check and info message to nvdimm post copy.
> > [7/7] migration/ram: ensure write persistence on loading all date to PMEM.
> > 
> > Haozhong:
> > [5/7] mem/nvdimm: ensure write persistence to PMEM in label emulation
> > 
> > Haozhong & Junyan:
> > [2/7] memory, exec: switch file ram allocation functions to 'flags' parameters
> > [3/7] configure: add libpmem support [4/7] hostmem-file: add the 'pmem' option
> > [4/7] hostmem-file: add the 'pmem' option
> > 
> > --
> > backends/hostmem-file.c | 44 ++++++++++++++++++++++++++++++++++++++++++--
> > configure               | 29 +++++++++++++++++++++++++++++
> > docs/nvdimm.txt         | 22 ++++++++++++++++++++++
> > exec.c                  | 38 +++++++++++++-------------------------
> > hw/mem/nvdimm.c         |  9 ++++++++-
> > include/exec/memory.h   | 31 +++++++++++++++++++++++++++++--
> > include/exec/ram_addr.h | 28 ++++++++++++++++++++++++++--
> > include/qemu/pmem.h     | 36 ++++++++++++++++++++++++++++++++++++
> > memory.c                |  8 +++++---
> > migration/ram.c         | 17 +++++++++++++++++
> > numa.c                  |  2 +-
> > qemu-options.hx         |  7 +++++++
> > 12 files changed, 235 insertions(+), 36 deletions(-)
> > create mode 100644 include/qemu/pmem.h
> > 
> > -- 
> > 2.7.4
> > 
> > 

  reply	other threads:[~2018-07-27 13:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  7:47 [Qemu-devel] [PATCH 0/7 V11] nvdimm: guarantee persistence of QEMU writes to persistent memory junyan.he
2018-07-18  7:47 ` [Qemu-devel] [PATCH 1/7 V11] memory, exec: Expose all memory block related flags junyan.he
2018-07-18  7:47 ` [Qemu-devel] [PATCH 2/7 V11] memory, exec: switch file ram allocation functions to 'flags' parameters junyan.he
2018-07-18 15:13   ` Richard Henderson
2018-07-18  7:47 ` [Qemu-devel] [PATCH 3/7 V11] configure: add libpmem support junyan.he
2018-07-18  7:48 ` [Qemu-devel] [PATCH 4/7 V11] hostmem-file: add the 'pmem' option junyan.he
2018-07-18  7:48 ` [Qemu-devel] [PATCH 5/7 V11] mem/nvdimm: ensure write persistence to PMEM in label emulation junyan.he
2018-07-18 15:15   ` Richard Henderson
2018-07-18  7:48 ` [Qemu-devel] [PATCH 6/7 V11] migration/ram: Add check and info message to nvdimm post copy junyan.he
2018-07-18  7:48 ` [Qemu-devel] [PATCH 7/7 V11] migration/ram: ensure write persistence on loading all data to PMEM junyan.he
2018-07-27 12:49 ` [Qemu-devel] [PATCH 0/7 V11] nvdimm: guarantee persistence of QEMU writes to persistent memory Stefan Hajnoczi
2018-07-27 13:06   ` Michael S. Tsirkin [this message]
2018-07-31 15:49     ` Stefan Hajnoczi

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=20180727160529-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=junyan.he@gmx.com \
    --cc=junyan.he@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=xiaoguangrong.eric@gmail.com \
    --cc=yi.z.zhang@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).