Skip to contentSkip to conversation

docs/nvdimm: add 'pmem=on' for the device dax backend file

PATCH In review Jingqi Liu 2 participants 2 messages Jul 30, 2020

lore
Share & tools
lore

Jingqi Liu

author
#0 lore raw

PATCH 1/1 docs/nvdimm: add 'pmem=on' for the device dax backend file

At the end of live migration, QEMU uses msync() to flush the data to the backend storage. When the backend file is a character device dax, the pages explicitly avoid the page cache. It will return failure from msync(). The following warning is output.

"warning: qemu_ram_msync: failed to sync memory range“

So we add 'pmem=on' to avoid calling msync(), use the QEMU command line:

    -object memory-backend-file,id=mem1,pmem=on,mem-path=/dev/dax0.0,size=4G
---
 docs/nvdimm.txt | 7 +++++++
 1 file changed, 7 insertions(+)
docs/nvdimm.txt +7 -0
index c2c6e441b3..31048aff5e 100644
@@ -243,6 +243,13 @@ use the QEMU command line:
 
     -object memory-backend-file,id=nv_mem,mem-path=/XXX/yyy,size=4G,pmem=on
 
+At the end of live migration, QEMU uses msync() to flush the data to the
+backend storage. When the backend file is a character device dax, the pages
+explicitly avoid the page cache. It will return failure from msync().
+So we add 'pmem=on' to avoid calling msync(), use the QEMU command line:
+
+    -object memory-backend-file,id=mem1,pmem=on,mem-path=/dev/dax0.0,size=4G
+
 References
 ----------
 
Signature · 1 line
2.17.1
Reviewed-by on v1 1/1
#1 lore raw
Quoted 26 lines

At the end of live migration, QEMU uses msync() to flush the data to the backend storage. When the backend file is a character device dax, the pages explicitly avoid the page cache. It will return failure from msync(). The following warning is output.

"warning: qemu_ram_msync: failed to sync memory range“

So we add 'pmem=on' to avoid calling msync(), use the QEMU command line:

    -object memory-backend-file,id=mem1,pmem=on,mem-path=/dev/dax0.0,size=4G
---
 docs/nvdimm.txt | 7 +++++++
 1 file changed, 7 insertions(+)
docs/nvdimm.txt +1 -0
index c2c6e441b3..31048aff5e 100644
@@ -243,6 +243,13 @@ use the QEMU command line:
 
     -object memory-backend-file,id=nv_mem,mem-path=/XXX/yyy,size=4G,pmem=on
 
+At the end of live migration, QEMU uses msync() to flush the data to the

docs/nvdimm.txt use the QEMU command line:

Quoted 10 lines
docs/nvdimm.txt +6 -1
+backend storage. When the backend file is a character device dax, the pages
+explicitly avoid the page cache. It will return failure from msync().
+So we add 'pmem=on' to avoid calling msync(), use the QEMU command line:
+
+    -object memory-backend-file,id=mem1,pmem=on,mem-path=/dev/dax0.0,size=4G
+
 References
 ----------
 
--

Good to document this.

Quoted 3 lines

2.17.1