mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-03 11:51:11 +00:00
173733b7a8
The virtio-pmem is a virtio variant of NVDIMM and just like NVDIMM virtio-pmem also allows accessing host pages bypassing guest page cache. The difference is that if a regular file is used to back guest's NVDIMM (model='nvdimm') the persistence of guest writes might not be guaranteed while with virtio-pmem it is. To express this new model at domain XML level, I've chosen the following: <memory model='virtio-pmem' access='shared'> <source> <path>/tmp/virtio_pmem</path> </source> <target> <size unit='KiB'>524288</size> </target> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memory> Another difference between NVDIMM and virtio-pmem is that while the former supports NUMA node locality the latter doesn't. And also, the latter goes onto PCI bus and not into a DIMM module. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com> |
||
---|---|---|
.. | ||
basictypes.rng | ||
capability.rng | ||
cpu.rng | ||
cputypes.rng | ||
domain.rng | ||
domainbackup.rng | ||
domaincaps.rng | ||
domaincheckpoint.rng | ||
domaincommon.rng | ||
domainsnapshot.rng | ||
interface.rng | ||
meson.build | ||
network.rng | ||
networkcommon.rng | ||
networkport.rng | ||
nodedev.rng | ||
nwfilter_params.rng | ||
nwfilter.rng | ||
nwfilterbinding.rng | ||
secret.rng | ||
storagecommon.rng | ||
storagepool.rng | ||
storagepoolcaps.rng | ||
storagevol.rng |