/Linux-v5.10/security/keys/ |
D | persistent.c | 43 struct key *persistent; in key_create_persistent() local 57 persistent = keyring_alloc(index_key->description, in key_create_persistent() 63 if (IS_ERR(persistent)) in key_create_persistent() 64 return ERR_CAST(persistent); in key_create_persistent() 66 return make_key_ref(persistent, true); in key_create_persistent() 77 struct key *persistent; in key_get_persistent() local 113 persistent = key_ref_to_ptr(persistent_ref); in key_get_persistent() 114 ret = key_link(key_ref_to_ptr(dest_ref), persistent); in key_get_persistent() 116 key_set_timeout(persistent, persistent_keyring_expiry); in key_get_persistent() 117 ret = persistent->serial; in key_get_persistent()
|
D | Makefile | 23 obj-$(CONFIG_PERSISTENT_KEYRINGS) += persistent.o
|
D | Kconfig | 43 bool "Enable register of persistent per-UID keyrings" 46 This option provides a register of persistent per-UID keyrings, 47 primarily aimed at Kerberos key storage. The keyrings are persistent
|
/Linux-v5.10/drivers/nvdimm/ |
D | Kconfig | 12 bus is registered to advertise PMEM (persistent memory) 35 these persistent memory ranges into block devices that are 48 apertures to access persistent media. 66 update semantics for persistent memory devices, so that 80 bool "PFN: Map persistent (device) memory" 85 Map persistent memory, i.e. advertise it to the memory 86 management sub-system. By default persistent memory does 95 bool "NVDIMM DAX: Raw access to persistent memory" 99 Support raw device dax access to a persistent memory 101 persistent memory, this capability provides a mechanism to [all …]
|
/Linux-v5.10/Documentation/devicetree/bindings/pmem/ |
D | pmem-region.txt | 1 Device-tree bindings for persistent memory regions 9 Given b) it is best to think of persistent memory as a kind of memory mapped 11 persistent regions separately to the normal memory pool. To aid with that this 12 binding provides a standardised interface for discovering where persistent 36 backed by non-persistent memory. This lets the OS know that it 38 persistent after a write.
|
/Linux-v5.10/drivers/dax/ |
D | Kconfig | 25 tristate "PMEM DAX: direct access to persistent memory" 29 Support raw access to persistent memory. Note that this 57 tristate "KMEM DAX: volatile-use of persistent memory" 62 Support access to persistent, or other performance 64 easier use of persistent memory by unmodified applications, or
|
/Linux-v5.10/Documentation/ABI/testing/ |
D | pstore | 5 Description: Generic interface to platform dependent persistent storage. 27 the file will signal to the underlying persistent storage 33 will be saved elsewhere and erased from persistent store 40 persistent storage until at least this amount is reached.
|
D | sysfs-driver-xen-blkback | 24 How long a persistent grant is allowed to remain 44 Whether to enable the persistent grants feature or not. Note
|
/Linux-v5.10/drivers/md/ |
D | dm-exception-store.c | 199 char persistent; in dm_exception_store_create() local 212 persistent = toupper(*argv[0]); in dm_exception_store_create() 213 if (persistent == 'P') in dm_exception_store_create() 215 else if (persistent == 'N') in dm_exception_store_create()
|
/Linux-v5.10/Documentation/admin-guide/device-mapper/ |
D | writecache.rst | 5 The writecache target caches writes on persistent memory or on SSD. It 16 - p - persistent memory 46 applicable only to persistent memory - use the FUA flag 47 when writing data from persistent memory back to the 50 applicable only to persistent memory - don't use the FUA
|
D | snapshot.rst | 34 - snapshot <origin> <COW device> <persistent?> <chunksize> 45 <persistent?> is P (Persistent) or N (Not persistent - will not survive 46 after reboot). O (Overflow) can be added as a persistent store option 50 The difference between persistent and transient is with transient 73 - snapshot-merge <origin> <COW device> <persistent> <chunksize> 77 works with persistent snapshots. This target assumes the role of the
|
D | persistent-data.rst | 20 The persistent-data library is an attempt to provide a re-usable 29 under drivers/md/persistent-data. 40 Clients of persistent-data are unlikely to use this directly.
|
D | index.rst | 29 persistent-data
|
/Linux-v5.10/drivers/gpio/ |
D | gpio-arizona.c | 31 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_in() local 42 if (change && persistent) { in arizona_gpio_direction_in() 101 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_out() local 109 if ((val & ARIZONA_GPN_DIR) && persistent) { in arizona_gpio_direction_out()
|
/Linux-v5.10/drivers/md/persistent-data/ |
D | Makefile | 2 obj-$(CONFIG_DM_PERSISTENT_DATA) += dm-persistent-data.o 3 dm-persistent-data-objs := \
|
/Linux-v5.10/Documentation/admin-guide/mm/ |
D | hugetlbpage.rst | 30 persistent hugetlb pages in the kernel's huge page pool. It also displays 77 ``/proc/sys/vm/nr_hugepages`` indicates the current number of "persistent" huge 80 privileges can dynamically allocate more or free some persistent huge pages 92 The administrator can allocate persistent huge pages on the kernel boot 152 default sized persistent huge pages:: 164 silently skipped when allocating persistent huge pages. See the 167 with the allocation and freeing of persistent huge pages. 190 persistent huge page pool is exhausted. As these surplus huge pages become 194 surplus pages will first be promoted to persistent huge pages. Then, additional 196 the new persistent huge page pool size. [all …]
|
/Linux-v5.10/include/uapi/linux/ |
D | cdrom.h | 764 __u8 persistent : 1; member 768 __u8 persistent : 1; member 791 __u8 persistent : 1; member 795 __u8 persistent : 1; member 921 __u8 persistent:1; member 925 __u8 persistent:1; member
|
/Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/ |
D | microchip,pic32-evic.txt | 27 internal interrupts use IRQ_TYPE_EDGE_RISING for non persistent interrupts and 28 IRQ_TYPE_LEVEL_HIGH for persistent interrupts. For external interrupts use
|
/Linux-v5.10/Documentation/driver-api/nvdimm/ |
D | firmware-activate.rst | 7 Some persistent memory devices run a firmware locally on the device / 12 persistent memory platform implementation, described by the Intel ACPI 86 [1]: https://docs.pmem.io/persistent-memory/
|
/Linux-v5.10/sound/soc/intel/catpt/ |
D | messages.c | 52 struct resource *persistent, in catpt_ipc_alloc_stream() argument 79 input.persistent_mem.offset = catpt_to_dsp_offset(persistent->start); in catpt_ipc_alloc_stream() 80 input.persistent_mem.size = resource_size(persistent); in catpt_ipc_alloc_stream()
|
/Linux-v5.10/Documentation/devicetree/bindings/reserved-memory/ |
D | ramoops.txt | 4 ramoops provides persistent RAM storage for oops and panics, so they can be 9 Parts of this storage may be set aside for other persistent log buffers, such
|
/Linux-v5.10/drivers/mtd/spi-nor/controllers/ |
D | Kconfig | 40 and is used to hold BIOS and other persistent settings. Using 56 Intel hardware and is used to hold BIOS and other persistent
|
/Linux-v5.10/net/rfkill/ |
D | core.c | 47 bool persistent; member 601 rfkill->persistent = true; in rfkill_init_sw_state() 630 rfkill->persistent = true; in rfkill_set_states() 701 return sprintf(buf, "%d\n", rfkill->persistent); in persistent_show() 703 static DEVICE_ATTR_RO(persistent); 882 if (!rfkill->persistent) { in rfkill_resume() 1048 if (!rfkill->persistent || rfkill_epo_lock_active) { in rfkill_register()
|
/Linux-v5.10/Documentation/filesystems/ |
D | dax.txt | 46 2. There exists a persistent flag FS_XFLAG_DAX that can be applied to regular 50 3. If the persistent FS_XFLAG_DAX flag is set on a directory, this flag will 86 6. When changing the S_DAX policy via toggling the persistent FS_XFLAG_DAX flag, 105 There are 2 per-file dax flags. One is a persistent inode setting (FS_XFLAG_DAX) 109 FS_XFLAG_DAX is preserved within the filesystem. This persistent config 187 - pmem: NVDIMM persistent memory driver
|
/Linux-v5.10/arch/arm/boot/dts/ |
D | facebook-bmc-flash-layout.dtsi | 26 * as persistent data store.
|