qemu/docs/nvdimm.txt

7 The current QEMU only implements the persistent memory mode of vNVDIMM
13 The storage of a vNVDIMM device in QEMU is provided by the memory
14 backend (i.e. memory-backend-file and memory-backend-ram). A simple
20  -object memory-backend-file,id=mem1,share=on,mem-path=$PATH,size=$NVDIMM_SIZE,readonly=off
34  - "object memory-backend-file,id=mem1,share=on,mem-path=$PATH,
50    virtual NVDIMM device whose storage is provided by above memory backend
63 detect a NVDIMM device which is in the persistent memory mode and whose
68 1. Prior to QEMU v2.8.0, if memory-backend-file is used and the actual
79    option of memory-backend-file, e.g. 4KB alignment on x86.  However,
82    change breaks the usage of memory-backend-file that only satisfies
86    architectures, so the broken memory-backend-file can work again.
102    If a memory backend file, which was previously used as the backend
120  (qemu) object_add memory-backend-file,id=mem2,share=on,mem-path=new_nvdimm.img,size=4G
125 1. Each hotplugged vNVDIMM device consumes one memory slot. Users
126    should always ensure the memory option "-m ...,slots=N" specifies
132 2. The similar is required for the memory option "-m ...,maxmem=M", i.e.
144 memory-backend-file to allow users to specify the proper alignment.
160  -object memory-backend-file,id=mem1,share=on,mem-path=/dev/dax0.0,size=4G,align=2M
172 When using B (A file supporting direct mapping of persistent memory)
235 "mem-ctrl" - The platform supports flushing dirty data from the memory
240              platform also supports flushing dirty data through the memory
243 If the vNVDIMM backend is in host persistent memory that can be accessed in
245 the 'pmem' option of memory-backend-file to 'on'. When 'pmem' is 'on' and QEMU
254     -object memory-backend-file,id=nv_mem,mem-path=/XXX/yyy,size=4G,pmem=on
262 [2] Persistent Memory Development Kit (PMDK), formerly known as NVML project, home page: