Home
last modified time | relevance | path

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

12

/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/linux/drivers/iio/light/
H A Dtsl2772.c1104 int ret = -EINVAL, count, persistence; in tsl2772_write_event_value() local
1144 persistence = ((val * 1000000) + val2) / in tsl2772_write_event_value()
1149 if (persistence > 3) in tsl2772_write_event_value()
1150 persistence = (persistence / 5) + 3; in tsl2772_write_event_value()
1152 chip->settings.als_persistence = persistence; in tsl2772_write_event_value()
1154 chip->settings.prox_persistence = persistence; in tsl2772_write_event_value()
1177 int filter_delay, persistence; in tsl2772_read_event_value() local
1209 persistence = chip->settings.als_persistence; in tsl2772_read_event_value()
1212 if (persistence > 3) in tsl2772_read_event_value()
1213 persistence = (persistence - 3) * 5; in tsl2772_read_event_value()
[all …]
/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/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/linux/drivers/s390/cio/
H A Dscm.c101 scm_attr(persistence);
142 scmdev->attrs.persistence = sale->p; in scmdev_setup()
/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/linux/arch/s390/include/asm/
H A Deadm.h90 unsigned int persistence:4; member
/openbmc/linux/drivers/net/hamradio/
H A D6pack.c112 unsigned char persistence; member
148 if (((sp->status1 & SIXP_DCD_MASK) == 0) && (random < sp->persistence)) { in sp_xmit_on_air()
196 case 2: sp->persistence = p[1]; in sp_encaps()
603 sp->persistence = SIXP_PERSIST; in sixpack_open()
/openbmc/linux/Documentation/networking/
H A Dipvs-sysctl.rst183 persistence template if it is to be used to schedule a new
296 Controls the synchronisation of connections when using persistence
302 for normal connections, do it only for persistence templates.
/openbmc/linux/drivers/dax/
H A DKconfig12 Support raw access to differentiated (persistence, bandwidth,
/openbmc/linux/Documentation/misc-devices/
H A Dbh1770glc.rst132 Filtered by persistence filter (prox0_thresh_above_count)
/openbmc/linux/Documentation/driver-api/usb/
H A Dpersist.rst3 USB device persistence during system suspend
78 reset or otherwise had lost power) then it applies a persistence check
/openbmc/linux/drivers/usb/core/
H A DKconfig24 Say N here if you don't want USB power session persistence
/openbmc/linux/net/netfilter/ipvs/
H A DKconfig346 tristate "SIP persistence engine"
350 Allow persistence based on the SIP Call-ID
/openbmc/openbmc-test-automation/redfish/account_service/
H A Dtest_user_account.robot32 [Documentation] Verify Redfish admin user persistence after reboot.
47 [Documentation] Verify Redfish operator user persistence after reboot.
62 [Documentation] Verify Redfish readonly user persistence after reboot.
/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/qemu/hw/core/
H A Dmachine.c656 nvdimms_state->persistence = 3; in machine_set_nvdimm_persistence()
658 nvdimms_state->persistence = 2; in machine_set_nvdimm_persistence()
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-nfit56 source or last "flush to persistence".
/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.
/openbmc/qemu/docs/about/
H A Ddeprecated.rst286 (without persistence guaranties) with backing file on non DAX storage
288 (to have NVDIMM with persistence guaranties).
/openbmc/linux/Documentation/filesystems/
H A Dpath-lookup.txt294 not required for dentry persistence.
298 refcounts are not required for persistence. Also we are free to perform mount
/openbmc/linux/Documentation/filesystems/nfs/
H A Dclient-identifier.rst180 "co_ownerid" string uniqueness and persistence is critical in this

12