Makes sense, but I have some questions about the details.
> Copy the state, and hotadd the persistent memory so machine still has all
> 8G for runtime. Before reboot, hotremove device-dax 2G, copy the memory
> that is needed to be preserved to pmem0 device, and reboot.
> The series of operations look like this:
> 1. After boot restore /dev/pmem0 to boot
s/boot/to a ramdisk from which is is picked by apps/
> 2. Convert raw pmem0 to devdax
> ndctl create-namespace --mode devdax --map mem -e namespace0.0 -f
> 3. Hotadd to System RAM
> echo dax0.0 > /sys/bus/dax/drivers/device_dax/unbind
> echo dax0.0 > /sys/bus/dax/drivers/kmem/new_id
> 4. Before reboot hotremove device-dax memory from System RAM
> echo dax0.0 > /sys/bus/dax/drivers/kmem/unbind
> 5. Create raw pmem0 device
> ndctl create-namespace --mode raw -e namespace0.0 -f
> 6. Copy the state to this device
What is the source of this copy? The state that was in the hot-added
memory? Isn't it "already there" since you effectively renamed dax0.0
Before hotremove, applications create a file in a ramdisk that is 2G
in size. After that applications, exist. We copy this file from
ramdisk to /dev/pmem0 (RAM to RAM copy) to be able to quickly restore
after reboot. After reboot, applications take that file from ramdisk,
and ramdisk is freed.
> 7. Do kexec reboot, or reboot through firmware, is firmware does not
> zero memory in pmem region.
Wouldn't the dax0.0 contents be preserved regardless? How does the
guest recover the pre-initialized state / how does the kernel know to
give out the same pages to the application as the previous boot?
On these machines we do not have real persistent memory, only regular
volatile RAM. So, kernel has to either be booted via memap arguments
that specify persistent range, or via special pmem device node in DTB.