qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: junyan.he@gmx.com, qemu-devel@nongnu.org,
	xiaoguangrong.eric@gmail.com, crosthwaite.peter@gmail.com,
	mst@redhat.com, ehabkost@redhat.com, quintela@redhat.com,
	Junyan He <junyan.he@intel.com>,
	stefanha@redhat.com, pbonzini@redhat.com, imammedo@redhat.com,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH V6 7/7] migration/ram: ensure write persistence on loading all data to PMEM.
Date: Thu, 7 Jun 2018 11:42:23 +0100	[thread overview]
Message-ID: <20180607104222.GH2522@work-vm> (raw)
In-Reply-To: <20180605114412.GE11888@stefanha-x1.localdomain>

* Stefan Hajnoczi (stefanha@gmail.com) wrote:
> On Fri, Jun 01, 2018 at 04:10:29PM +0800, junyan.he@gmx.com wrote:
> > diff --git a/migration/ram.c b/migration/ram.c
> > index aa0c6f0..09525b2 100644
> > --- a/migration/ram.c
> > +++ b/migration/ram.c
> > @@ -33,6 +33,7 @@
> >  #include "qemu/bitops.h"
> >  #include "qemu/bitmap.h"
> >  #include "qemu/main-loop.h"
> > +#include "qemu/pmem.h"
> >  #include "xbzrle.h"
> >  #include "ram.h"
> >  #include "migration.h"
> > @@ -3046,6 +3047,13 @@ static int ram_load_setup(QEMUFile *f, void *opaque)
> >  static int ram_load_cleanup(void *opaque)
> >  {
> >      RAMBlock *rb;
> > +
> > +    RAMBLOCK_FOREACH(rb) {
> > +        if (ramblock_is_pmem(rb)) {
> > +            pmem_persist(rb->host, rb->used_length);
> > +         }
> 
> Indentation is off.  This can be fixed by the maintainer who merges
> these patches.
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>


The other thing that needs a fixup for is RAMBLOCK_FOREACH_MIGRATABLE
that recently got merged.

Dave

--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-06-07 10:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  8:10 [Qemu-devel] [PATCH V6 0/7] nvdimm: guarantee persistence of QEMU writes to persistent memory junyan.he
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 1/7] memory, exec: Expose all memory block related flags junyan.he
2018-06-05 11:38   ` Stefan Hajnoczi
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 2/7] memory, exec: switch file ram allocation functions to 'flags' parameters junyan.he
2018-06-05 11:40   ` Stefan Hajnoczi
2018-06-11 15:53   ` Igor Mammedov
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 3/7] hostmem-file: add the 'pmem' option junyan.he
2018-06-05 11:44   ` Stefan Hajnoczi
2018-06-11 16:02   ` Igor Mammedov
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 4/7] configure: add libpmem support junyan.he
2018-06-05 11:41   ` Stefan Hajnoczi
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 5/7] mem/nvdimm: ensure write persistence to PMEM in label emulation junyan.he
2018-06-05 11:44   ` Stefan Hajnoczi
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 6/7] migration/ram: Add check and info message to nvdimm post copy junyan.he
2018-06-05 11:44   ` Stefan Hajnoczi
2018-06-01  8:10 ` [Qemu-devel] [PATCH V6 7/7] migration/ram: ensure write persistence on loading all data to PMEM junyan.he
2018-06-05 11:44   ` Stefan Hajnoczi
2018-06-07 10:42     ` Dr. David Alan Gilbert [this message]
2018-06-01  8:27 ` [Qemu-devel] [PATCH V6 0/7] nvdimm: guarantee persistence of QEMU writes to persistent memory no-reply
2018-06-07 13:50   ` Stefan Hajnoczi
2018-06-01  8:33 ` no-reply
2018-06-12 12:06 ` Igor Mammedov
2018-06-12 13:38   ` Junyan He
2018-06-12 14:55     ` Igor Mammedov
2018-06-12 15:27       ` Junyan He
2018-06-12 15:43         ` Junyan He
2018-06-13 15:58           ` Igor Mammedov
2018-06-13 20:05     ` Eduardo Habkost

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=20180607104222.GH2522@work-vm \
    --to=dgilbert@redhat.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=junyan.he@gmx.com \
    --cc=junyan.he@intel.com \
    --cc=mst@redhat.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 \
    /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).