| commit | cdcf766d0b0364165ba9e5ceacfdf37c8b1fe4ae | |
| author | Igor Mammedov <imammedo@redhat.com> | |
| Mon, 11 Jan 2021 20:33:32 +0000 (11 15:33 -0500) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Tue, 6 Jul 2021 22:05:16 +0000 (6 18:05 -0400) | ||
| tree | 27dae453b720de1bc58c6eb425f9efbf996f9b3e | treesnapshot (tar.gz zip) |
| parent | 80cc1a0dd19cc414ddaa3f1b9b6ef91e3ebc12b2 | commitdiff |
Deprecate pmem=on with non-DAX capable backend file
It is not safe to pretend that emulated NVDIMM supports
persistence while backend actually failed to enable it
and used non-persistent mapping as fall back.
Instead of falling-back, QEMU should be more strict and
error out with clear message that it's not supported.
So if user asks for persistence (pmem=on), they should
store backing file on NVDIMM.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210111203332.740815-1-imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
It is not safe to pretend that emulated NVDIMM supports
persistence while backend actually failed to enable it
and used non-persistent mapping as fall back.
Instead of falling-back, QEMU should be more strict and
error out with clear message that it's not supported.
So if user asks for persistence (pmem=on), they should
store backing file on NVDIMM.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210111203332.740815-1-imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| docs/system/deprecated.rst | diffblobblamehistory | |
| util/mmap-alloc.c | diffblobblamehistory |