| /linux/security/keys/ |
| H A D | persistent.c | 2 /* General persistent per-UID keyrings register
16 * Create the persistent keyring register for the current user namespace.
36 * Create the persistent keyring for the specified user.
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()
70 * Get the persistent keyring for a specific UID and link it to the nominated
77 struct key *persistent; in key_get_persistent() local
[all …]
|
| /linux/drivers/nvdimm/ |
| H A D | Kconfig | 12 bus is registered to advertise PMEM (persistent memory)
20 tristate "PMEM: Persistent memory block device support"
32 these persistent memory ranges into block devices that are
50 update semantics for persistent memory devices, so that
63 bool "PFN: Map persistent (device) memory"
68 Map persistent memory, i.e. advertise it to the memory
69 management sub-system. By default persistent memory does
78 bool "NVDIMM DAX: Raw access to persistent memory"
82 Support raw device dax access to a persistent memory
84 persistent memory, this capability provides a mechanism to
[all …]
|
| /linux/tools/testing/selftests/pidfd/ |
| H A D | pidfd_xattr_test.c | 103 …ret = fsetxattr(self->child_pidfd, "trusted.persistent", "persistent value", strlen("persistent va… in TEST_F()
107 ret = fgetxattr(self->child_pidfd, "trusted.persistent", buf, sizeof(buf)); in TEST_F()
108 ASSERT_EQ(ret, strlen("persistent value")); in TEST_F()
109 ASSERT_EQ(strcmp(buf, "persistent value"), 0); in TEST_F()
113 ASSERT_EQ(strcmp(list, "trusted.persistent"), 0) in TEST_F()
123 ret = fgetxattr(self->child_pidfd, "trusted.persistent", buf, sizeof(buf)); in TEST_F()
124 ASSERT_EQ(ret, strlen("persistent value")); in TEST_F()
125 ASSERT_EQ(strcmp(buf, "persistent value"), 0); in TEST_F()
129 ASSERT_EQ(strcmp(list, "trusted.persistent"), 0); in TEST_F()
|
| /linux/Documentation/devicetree/bindings/pmem/ |
| H A D | pmem-region.yaml | 10 title: Persistent Memory Regions
13 Persistent memory refers to a class of memory devices that are:
18 Given b) it is best to think of persistent memory as a kind of memory mapped
20 persistent regions separately to the normal memory pool. To aid with that this
21 binding provides a standardised interface for discovering where persistent
33 Indicates the region is volatile (non-persistent) and the OS can skip
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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
|
| H A D | writecache.rst | 5 The writecache target caches writes on persistent memory or on SSD. It
15 - p - persistent memory
45 applicable only to persistent memory - use the FUA flag
46 when writing data from persistent memory back to the
49 applicable only to persistent memory - don't use the FUA
|
| H A D | persistent-data.rst | 2 Persistent data
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.
|
| /linux/drivers/scsi/ |
| H A D | constants.c | 71 /* 5c-5f */ "Read buffer capacity", "Send cue sheet", "Persistent reserve in",
72 "Persistent reserve out",
160 {0x0, "Persistent reserve in, read keys"},
161 {0x1, "Persistent reserve in, read reservation"},
162 {0x2, "Persistent reserve in, report capabilities"},
163 {0x3, "Persistent reserve in, read full status"},
168 {0x0, "Persistent reserve out, register"},
169 {0x1, "Persistent reserve out, reserve"},
170 {0x2, "Persistent reserve out, release"},
171 {0x3, "Persistent reserve out, clear"},
[all …]
|
| /linux/fs/pstore/ |
| H A D | Kconfig | 3 tristate "Persistent store support"
7 persistent storage via "pstore" filesystem that can
11 (or "M") to a platform specific persistent store driver
13 If you don't have a platform persistent store driver,
56 bool "Persistent function tracer"
61 With this option kernel traces function calls into a persistent
|
| /linux/include/uapi/linux/ |
| H A D | ip_vs.h | 21 #define IP_VS_SVC_F_PERSISTENT 0x0001 /* persistent port */
154 unsigned int timeout; /* persistent timeout in sec */
155 __be32 netmask; /* persistent netmask */
216 unsigned int timeout; /* persistent timeout */
217 __be32 netmask; /* persistent netmask */
238 __u32 persistconns; /* persistent connections */
368 IPVS_SVC_ATTR_TIMEOUT, /* persistent timeout */
369 IPVS_SVC_ATTR_NETMASK, /* persistent netmask */
400 IPVS_DEST_ATTR_PERSIST_CONNS, /* persistent connections */
|
| /linux/Documentation/block/ |
| H A D | pr.rst | 2 Block layer support for Persistent Reservations
6 Persistent Reservations which map to block devices that support
7 these (like SCSI). Persistent Reservations allow restricting
14 "PERSISTENT RESERVE IN" and "PERSISTENT RESERVE OUT" commands.
|
| /linux/Documentation/networking/ |
| H A D | net_failover.rst | 48 <teaming type='persistent'/>
56 <teaming type='transient' persistent='ua-backup0'/>
60 interface and this acts as the 'persistent' device indicating that this
62 required attribute type having value 'persistent'. The link state for the
69 periodically be unplugged. A second attribute - 'persistent' is provided and
132 <teaming type='transient' persistent='ua-backup0'/>
162 virsh migrate --live --persistent $DOMAIN qemu+ssh://$REMOTE_HOST/system
|
| /linux/drivers/cxl/ |
| H A D | Kconfig | 29 this class code provide support for volatile and / or persistent
74 hierarchy to map regions that represent System RAM, or Persistent
80 tristate "CXL PMEM: Persistent Memory Support"
85 support for persistent memory attached via CXL. This support is
88 provisioning the persistent memory capacity of CXL memory expanders.
97 RAM" and/or "Persistent Memory" that is fully coherent as if the
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | pmem.c | 4 * Handles hot and cold plug of persistent memory regions on pseries.
112 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in dlpar_hp_pmem()
142 { .type = "ibm,persistent-memory", },
154 pmem_node = of_find_node_by_type(NULL, "ibm,persistent-memory"); in pseries_pmem_init()
|
| /linux/drivers/md/ |
| H A D | dm-exception-store.c | 200 char persistent; in dm_exception_store_create() local
213 persistent = toupper(*argv[0]); in dm_exception_store_create()
214 if (persistent == 'P') in dm_exception_store_create()
216 else if (persistent == 'N') in dm_exception_store_create()
275 DMERR("Unable to register persistent exception store type"); in dm_exception_store_init()
|
| H A D | dm-snap-persistent.c | 20 #define DM_MSG_PREFIX "persistent snapshot"
27 * Persistent snapshots, by persistent we mean that the snapshot
57 * Magic for persistent snapshots: "SnAp" - Feeble isn't it.
103 * The top level structure for a persistent exception store.
887 DMERR("Unsupported persistent store option: %s", options); in persistent_ctr()
927 .name = "persistent",
962 DMERR("Unable to register persistent exception store type"); in dm_persistent_snapshot_init()
968 DMERR("Unable to register old-style persistent exception store type"); in dm_persistent_snapshot_init()
|
| /linux/drivers/gpio/ |
| H A D | gpio-arizona.c | 30 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_in() local
41 if (change && persistent) { in arizona_gpio_direction_in()
98 bool persistent = gpiochip_line_is_persistent(chip, offset); in arizona_gpio_direction_out() local
106 if ((val & ARIZONA_GPN_DIR) && persistent) { in arizona_gpio_direction_out()
|
| /linux/tools/testing/selftests/powerpc/tm/ |
| H A D | tm.h | 41 * Bit 7 (Failure Persistent) and Bit 15 (Implementation-specific).
48 * Per the ISA, the Failure Persistent bit may be incorrect. Try a few in htm_is_synthetic()
51 * should not be persistent. in htm_is_synthetic()
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A 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/drivers/md/persistent-data/ |
| H A D | Makefile | 2 obj-$(CONFIG_DM_PERSISTENT_DATA) += dm-persistent-data.o
3 dm-persistent-data-objs := \
|
| /linux/Documentation/admin-guide/ |
| H A D | ramoops.rst | 13 needs a system with persistent RAM so that the content of that area can
54 Ramoops also supports software ECC protection of persistent memory regions.
155 Persistent function tracing
158 Persistent function tracing might be useful for debugging software or hardware
|
| /linux/Documentation/ABI/testing/ |
| H A 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/drivers/block/xen-blkback/ |
| H A D | blkback.c | 77 * When the list of persistent grants is full we clean it up using a LRU
87 * How long a persistent grant is allowed to remain allocated without being in
95 "Time in seconds an unused persistent grant is allowed to "
116 * The LRU mechanism to clean the lists of persistent grants needs to
123 * When the persistent grants list is full we will remove unused grants
159 * We don't need locking around the persistent grant helpers
165 * bit operations to modify the flags of a persistent grant and to count
353 pr_debug("Going to purge at least %u persistent grants\n", in purge_persistent_gnt()
634 * Remove persistent grants and empty the pool of free pages
638 /* Free all persistent grant pages */ in xen_blkbk_free_caches()
[all …]
|
| /linux/Documentation/driver-api/cxl/allocation/ |
| H A D | dax.rst | 8 CXL allocator, or to managed shared or persistent memory regions across multiple
11 If the capacity is shared across hosts or persistent, appropriate flushing
|
| /linux/Documentation/trace/coresight/ |
| H A D | panic.rst | 32 and disabled cases are handled. Also, platforms that support persistent
85 itself. Persistent RAM is not a requirement in this case.
87 5. For platforms that supports persistent RAM, trace data can be dumped
89 Crashdump kernel is not a requirement in this case. Persistent RAM
102 has to be in persistent RAM.
|