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...@gmx.com wrote: > > > From: Junyan He <junyan...@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
signature.asc
Description: PGP signature
