From: Richard Henderson <richard.henderson@linaro.org>
To: junyan.he@gmx.com, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, imammedo@redhat.com, pbonzini@redhat.com,
crosthwaite.peter@gmail.com, xiaoguangrong.eric@gmail.com,
mst@redhat.com, quintela@redhat.com, dgilbert@redhat.com,
stefanha@redhat.com, yi.z.zhang@intel.com,
Junyan He <junyan.he@intel.com>,
Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: [Qemu-devel] [PATCH 5/7 V11] mem/nvdimm: ensure write persistence to PMEM in label emulation
Date: Wed, 18 Jul 2018 08:15:44 -0700 [thread overview]
Message-ID: <4ec0c65c-8e83-b2f0-19eb-3da65c148ce3@linaro.org> (raw)
In-Reply-To: <1531900083-18167-6-git-send-email-junyan.he@gmx.com>
On 07/18/2018 12:48 AM, junyan.he@gmx.com wrote:
> From: Junyan He <junyan.he@intel.com>
>
> Guest writes to vNVDIMM labels are intercepted and performed on the
> backend by QEMU. When the backend is a real persistent memort, QEMU
> needs to take proper operations to ensure its write persistence on the
> persistent memory. Otherwise, a host power failure may result in the
> loss of guest label configurations.
>
> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/mem/nvdimm.c | 9 ++++++++-
> include/qemu/pmem.h | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 38 insertions(+), 1 deletion(-)
> create mode 100644 include/qemu/pmem.h
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2018-07-18 15:15 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 [this message]
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
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=4ec0c65c-8e83-b2f0-19eb-3da65c148ce3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=haozhong.zhang@intel.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=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).