Home
last modified time | relevance | path

Searched refs:persistence (Results 1 – 17 of 17) sorted by relevance

/openbmc/qemu/docs/system/devices/
H A Dvirtio-pmem.rst22 specification. The virtio pmem device provides guest write persistence
61 Guest data persistence on non-NVDIMM requires guest userspace applications
68 a hint to application to perform fsync for write persistence.
/openbmc/qemu/docs/
H A Dnvdimm.txt167 the only backend that can guarantee the guest write persistence is:
173 as a backend, write persistence is guaranteed if the host kernel has
180 is not supported by the host kernel, write persistence is not
228 NVDIMM data persistence. Users can provide a persistence value to a guest via
229 the optional "nvdimm-persistence" machine command line option:
231 -machine pc,accel=kvm,nvdimm,nvdimm-persistence=cpu
247 will take necessary operations to guarantee the persistence of its own writes
250 a "lack of libpmem support" message to ensure the persistence is available.
251 For example, if we want to ensure the persistence for some backend file,
/openbmc/openbmc/meta-arm/meta-arm-bsp/dynamic-layers/meta-arm-systemready/recipes-test/arm-systemready-acs/files/fvp-base/
H A D0001-check-sr-results-Change-the-expected-SR-result-confi.patch14 a. must-have-esp: EFI partition/variable persistence not supported due to
20 EFI variables": EFI partition/variable persistence not supported due to
28 "EFI_SYSTEM_RESOURCE_ENTRY": EFI partition/variable persistence not
46 a. must-contain "EFISystemPartition": EFI partition/variable persistence
/openbmc/qemu/include/hw/mem/
H A Dnvdimm.h145 int32_t persistence; member
/openbmc/openpower-dbus-interfaces/xyz/openbmc_project/Common/FactoryReset/
H A DREADME.md17 The host software updater factory reset immediately clears persistence files
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/FactoryReset/
H A DREADME.md23 clears any volumes and persistence files created by the BMC processes. This
/openbmc/qemu/hw/acpi/
H A Dnvdimm.c363 if (state->persistence) { in nvdimm_build_device_structure()
364 nvdimm_build_structure_caps(structures, state->persistence); in nvdimm_build_device_structure()
/openbmc/openbmc-test-automation/extended/code_update/
H A Dbmc_code_update.robot68 # Let the remaining test cases know we are doing a persistence test so we
/openbmc/qemu/docs/interop/
H A Dbitmaps.rst71 However, qcow2 is only strictly necessary for the persistence feature, which
72 writes bitmap data to disk upon close. If persistence is not required for a
73 specific use case, all bitmap features excepting persistence are available for
196 persistence, and recording state can be adjusted at creation time.
H A Dfirmware.json287 # persistence.
/openbmc/qemu/hw/core/
H A Dmachine.c704 nvdimms_state->persistence = 3; in machine_set_nvdimm_persistence()
706 nvdimms_state->persistence = 2; in machine_set_nvdimm_persistence()
/openbmc/qemu/docs/about/
H A Ddeprecated.rst390 (without persistence guaranties) with backing file on non DAX storage
392 (to have NVDIMM with persistence guaranties).
/openbmc/openbmc-test-automation/redfish/account_service/
H A Dtest_user_account.robot33 [Documentation] Verify Redfish admin user persistence after reboot.
51 [Documentation] Verify Redfish operator user persistence after reboot.
/openbmc/u-boot/scripts/
H A Dspelling.txt846 persistance||persistence
/openbmc/openbmc-test-automation/openpower/pel/
H A Dtest_bmc_pel.robot100 [Documentation] Verify PEL log persistence after BMC reboot.
/openbmc/openbmc/poky/documentation/overview-manual/
H A Dconcepts.rst2220 memory gives persistence between tasks and builds, which is not
/openbmc/qemu/
H A Dqemu-options.hx5628 operations to guarantee the persistence of its own writes to