Julia Suvorova d0180f0acb hw/mem/nvdimm: fix error message for 'unarmed' flag ... In the ACPI specification [1], the 'unarmed' bit is set when a device cannot accept a persistent write. This means that when a memdev is read-only, the 'unarmed' flag must be turned on. The logic is correct, just changing the error message. [1] ACPI NFIT NVDIMM Region Mapping Structure "NVDIMM State Flags" Bit 3 Fixes: dbd730e859 ("nvdimm: check -object memory-backend-file, readonly=on option") Signed-off-by: Julia Suvorova <jusual@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Acked-by: David Hildenbrand <david@redhat.com> Message-Id: <20221023195812.15523-1-jusual@redhat.com> Signed-off-by: David Hildenbrand <david@redhat.com>		2022-10-24 12:38:38 +02:00
..
cxl_type3.c	mem/cxl-type3: Add sn option to provide serial number for PCI ecap	2022-10-09 16:38:45 -04:00
Kconfig	hw/cxl/device: Add a memory device (8.2.8.5)	2022-05-13 06:13:36 -04:00
memory-device.c
meson.build	hw/cxl/device: Add a memory device (8.2.8.5)	2022-05-13 06:13:36 -04:00
npcm7xx_mc.c
nvdimm.c	hw/mem/nvdimm: fix error message for 'unarmed' flag	2022-10-24 12:38:38 +02:00
pc-dimm.c
sparse-mem.c
trace-events
trace.h