From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
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>,
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: Tue, 31 Jul 2018 16:49:06 +0100 [thread overview]
Message-ID: <20180731154906.GG17816@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180727160529-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Fri, Jul 27, 2018 at 04:06:23PM +0300, Michael S. Tsirkin wrote:
> 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.
I agree, it's too late for QEMU 3.0.
Have you considered keeping a -next tree? It's more
contributor-friendly if you merge patches into a -next tree so they
don't need to worry about it anymore.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-07-31 15:49 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
2018-07-31 15:49 ` Stefan Hajnoczi [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=20180731154906.GG17816@stefanha-x1.localdomain \
--to=stefanha@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=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=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).