Home
last modified time | relevance | path

Searched full:protected (Results 1 – 25 of 1193) sorted by relevance

12345678910>>...48

/linux/drivers/crypto/
H A DKconfig79 tristate "Kernel API for protected key handling"
83 for creation and handling of protected keys. Other parts of the
86 The protected key support is distributed into:
90 implementations using protected key.
92 loaded when pckmo support (that is generation of protected keys
100 protected execution environment.
103 API for protected key handling.
110 This is the CCA support handler for deriving protected keys
112 way to make protected keys from clear key values.
118 this option unless you are sure you never need to derive protected
[all …]
/linux/Documentation/virt/kvm/s390/
H A Ds390-pv-boot.rst4 s390 (IBM Z) Boot/IPL of Protected VMs
9 The memory of Protected Virtual Machines (PVMs) is not accessible to
17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
44 Subcode 10: Move into Protected Virtualization mode
67 When running in protected virtualization mode, some subcodes will result in
76 Re-IPL into a protected mode is only possible via a detour into non
77 protected mode.
/linux/arch/s390/kvm/
H A Dpv.c3 * Hosting Protected Virtual Machines
53 * No export is needed also when there is only one protected VM, because the
63 * shared page from a different protected VM will automatically also in should_export_before_import()
198 * struct pv_vm_to_be_destroyed - Represents a protected VM that needs to
202 * @old_gmap_table: the gmap table of the leftover protected VM
203 * @handle: the handle of the leftover protected VM
204 * @stor_var: pointer to the variable storage of the leftover protected VM
205 * @stor_base: address of the base storage of the leftover protected VM
207 * Represents a protected VM that is still registered with the Ultravisor,
364 * kvm_s390_pv_dispose_one_leftover - Clean up one leftover protected VM.
[all …]
/linux/include/drm/
H A Ddrm_auth.h51 * @unique: Unique identifier: e.g. busid. Protected by
56 * @unique_len: Length of unique field. Protected by
61 * @magic_map: Map of used authentication tokens. Protected by
87 * Protected by &drm_device.mode_config's &drm_mode_config.idr_mutex.
95 * Not used for owners. Protected by &drm_device.mode_config's
103 * List of drm_masters leasing from this one. Protected by
115 * Objects leased to this drm_master. Protected by
127 * Protected by &drm_device.mode_config's &drm_mode_config.idr_mutex.
/linux/arch/s390/include/uapi/asm/
H A Dpkey.h24 #define PROTKEYBLOBSIZE 80 /* protected key blob size is always 80 bytes */
25 #define MAXPROTKEYSIZE 64 /* a protected key blob may be up to 64 bytes */
94 /* Struct to hold protected key and length info */
98 __u8 protkey[MAXPROTKEYSIZE]; /* the protected key blob */
146 * Fabricate AES protected key from a CCA AES secure key
152 struct pkey_protkey protkey; /* out: the protected key */
158 * Fabricate AES protected key from clear key value
163 struct pkey_protkey protkey; /* out: the protected key */
185 struct pkey_protkey protkey; /* out: the protected key */
211 * Generate AES random protected key.
[all …]
/linux/rust/kernel/sync/
H A Dlocked_by.rs3 //! A wrapper for data protected by a lock that does not wrap it.
11 /// In most cases, data protected by a lock is wrapped by the appropriate lock type, e.g.,
14 /// to be protected by the same lock.
98 /// that the right owner is being used to access the protected data. If the owner is freed, the
101 /// because in any case at most one thread (or CPU) can access the protected data at a time.
115 /// Returns a reference to the protected data when the caller provides evidence (via a
119 /// the data protected by the lock without actually holding it.
123 /// Panics if `owner` is different from the data protected by the lock used in
144 /// Returns a mutable reference to the protected data when the caller provides evidence (via a
148 /// matches the data protected by the lock without actually holding it.
[all …]
H A Dlock.rs29 /// - Implementers must ensure that only one thread/CPU may access the protected data once the lock
117 /// The data protected by the lock.
172 /// Acquires the lock and gives the caller access to the data protected by it. in lock()
184 /// Returns a guard that can be used to access the data protected by the lock if successful.
199 /// protected by the lock.
207 // SAFETY: `Guard` is sync when the data protected by the lock is also sync.
252 /// Returns a pinned mutable reference to the protected data.
283 // SAFETY: The caller owns the lock, so it is safe to deref the protected data.
294 // SAFETY: The caller owns the lock, so it is safe to deref the protected data.
/linux/net/mac80211/tests/
H A Dmfp.c77 /* protected dual of public action */
79 .desc = "protected dual: drop unicast from unknown peer",
87 .desc = "protected dual: drop multicast from unknown peer",
95 .desc = "protected dual: drop unicast without MFP",
104 .desc = "protected dual: drop multicast without MFP",
113 .desc = "protected dual: drop undecrypted unicast with MFP",
123 .desc = "protected dual: drop undecrypted multicast with MFP",
133 .desc = "protected dual: accept unicast with MFP",
144 .desc = "protected dual: accept multicast with MFP",
/linux/drivers/virt/vboxguest/
H A Dvboxguest_core.h111 * Protected by session_mutex.
116 * Protected by session_mutex.
133 * Protected by session_mutex.
138 * Protected by session_mutex.
167 * Protected by vbg_gdev.session_mutex.
173 * host filter. Protected by vbg_gdev.session_mutex.
184 * host. Protected by vbg_gdev.session_mutex.
189 /** Set on CANCEL_ALL_WAITEVENTS, protected by vbg_devevent_spinlock. */
/linux/arch/arm64/kernel/
H A Drsi.c70 * protected memory. We should take extra care to ensure that we DO NOT in arm64_rsi_setup_memory()
74 * protected has failed here, then future accesses to the memory are in arm64_rsi_setup_memory()
81 panic("Failed to set memory range to protected: %pa-%pa", in arm64_rsi_setup_memory()
88 * Check if a given PA range is Trusted (e.g., Protected memory, a Trusted Device
92 * protected.
96 * RIPAS_RAM - Memory (RAM), protected by the RMM guarantees. (e.g., Firmware
/linux/Documentation/pcmcia/
H A Dlocking.rst62 protected by pcmcia_socket_list_rwsem;
67 The resource_ops and their data are protected by ops_mutex.
69 The "main" struct pcmcia_socket is protected as follows (read-only fields
112 The "main" struct pcmcia_device is protected as follows (read-only fields
/linux/include/linux/
H A Dcgroup-defs.h209 * linkage is protected by cgroup_mutex or RCU
250 * Protected by cgroup_mutex.
259 * Protected by rstat_base_lock when css is cgroup::self.
260 * Protected by css->ss->rstat_ss_lock otherwise.
294 /* internal task count, protected by css_set_lock */
300 * process of being migrated out or in. Protected by
326 * slot. Protected by css_set_lock
332 * css_set. Protected by css_set_lock.
338 * source or destination. Protected by cgroup_mutex.
349 * on this cset should be migrated to. Protected by cgroup_mutex.
[all …]
H A Dsrcu.h216 * No-op helper to denote that ssp must be held. Because SRCU-protected pointers
225 * srcu_dereference_check - fetch SRCU-protected pointer for later dereferencing
247 * srcu_dereference - fetch SRCU-protected pointer for later dereferencing
267 * srcu_read_lock - register a new reader for an SRCU-protected structure.
299 * srcu_read_lock_fast - register a new reader for an SRCU-protected structure.
391 * srcu_down_read_fast - register a new reader for an SRCU-protected structure.
411 * srcu_read_lock_nmisafe - register a new reader for an SRCU-protected structure. in srcu_read_lock_nmisafe()
445 * srcu_down_read - register a new reader for an SRCU-protected structure.
475 * srcu_read_unlock - unregister a old reader from an SRCU-protected structure.
491 * srcu_read_unlock_fast - unregister a old reader from an SRCU-protected structur
[all...]
H A Diocontext.h57 * - ioc->icq_list and icq->ioc_node are protected by ioc lock.
60 * - ioc->icq_tree and ioc->icq_hint are protected by ioc lock, while icq
61 * itself is protected by q lock. However, both the indexes and icq
106 /* all the fields below are protected by this lock */
H A Duprobes.h77 HPROBE_LEASED, /* uretprobes_srcu-protected uprobe */
85 * SRCU protected (with SRCU protection eventually potentially timing out),
89 * atomically "downgrade" temporarily RCU-protected uprobe into refcounted one
98 * SRCU-protected;
101 * protected initially, but SRCU period timed out and we attempted to
109 * When uprobe is SRCU-protected, we also record srcu_idx value, necessary for
/linux/net/ieee802154/
H A Dcore.h14 /* also protected by devlist_mtx */
18 /* protected by RTNL only */
21 /* associated wpan interfaces, protected by rtnl or RCU */
/linux/arch/arm64/kvm/hyp/nvhe/
H A Dpkvm.c26 * The currently loaded hyp vCPU for each physical CPU. Used in protected mode
27 * for both protected and non-protected VMs.
132 * enabled for protected VMs.
138 /* No AArch32 support for protected guests. */ in pkvm_check_pvm_cpu_features()
159 * Initialize trap register values in protected mode.
173 /* Trust the host for non-protected vcpu features. */ in pkvm_vcpu_init_traps()
218 * A table that tracks all VMs in protected mode.
336 /* CTR_EL0 is always under host control, even for protected VMs. */ in pkvm_init_features_from_host()
342 /* No restrictions for non-protected VMs. */ in pkvm_init_features_from_host()
563 * Initializing protected state might have failed, yet a malicious in allocate_vm_table_entry()
[all …]
/linux/arch/x86/kernel/
H A Dumip.c2 * umip.c Emulation for instruction protected by the User-Mode Instruction
27 * the UMIP-protected instructions (in the form of a SIGSEGV signal), it can be
38 * The instructions protected by UMIP can be split in two groups. Those which
107 * UMIP-protected instructions. Thus, the printed text is prepended with the
137 * identify_insn() - Identify a UMIP-protected instruction
140 * From the opcode and ModRM.reg in @insn identify, if any, a UMIP-protected
145 * On success, a constant identifying a specific UMIP-protected instruction that
148 * -EINVAL on error or when not an UMIP-protected instruction that can be
205 * Emulate an instruction protected by UMIP and provide a dummy result. The
/linux/drivers/gpu/drm/i915/pxp/
H A Dintel_pxp.c27 * PXP (Protected Xe Path) is a feature available in Gen12 and newer platforms.
28 * It allows execution and flip to display of protected (i.e. encrypted)
33 * correctly protected they must be used in conjunction with a context created
37 * Protected objects are tied to a pxp session; currently we only support one
40 * protected objects.
43 * session are marked as invalid and all contexts marked as using protected
152 drm_info(&gt->i915->drm, "Protected Xe Path (PXP) protected content support initialized\n"); in pxp_init_full()
499 /* ban all contexts marked as protected */ in intel_pxp_invalidate()
/linux/arch/arm64/kvm/
H A DKconfig56 bool "Protected KVM hypervisor stacktraces"
62 If using protected nVHE mode, but cannot afford the associated
66 If unsure, or not using protected nVHE (pKVM), say N.
/linux/drivers/gpu/drm/xe/
H A Dxe_vm_types.h72 * for migration on a SVM page-fault. The pointer is protected by the
124 * protected by BO's resv and for userptrs, vm->svm.gpusvm.notifier_lock in
137 * protected by vm->lock, vm->resv and for userptrs,
249 * @rebind_list: list of VMAs that need rebinding. Protected by the
286 * due to no work available. Protected by the vm resv.
329 * Protected by the VM's resv for writing. Opportunistic reading can be done
337 * Protected by the vm's resv.
344 * protected by the vm resv.
/linux/drivers/mtd/spi-nor/
H A DKconfig47 power-up or a reset the flash is software write protected by
65 protected or will be automatically software write protected after
/linux/Documentation/filesystems/
H A Dfiles.rst10 Up until 2.6.12, the file descriptor table has been protected
12 ->file_lock protected accesses to all the file related fields
18 The files (struct file) themselves are protected using
58 2. Reading of the fdtable as described above must be protected
/linux/Documentation/RCU/
H A Dchecklist.rst66 As a rough rule of thumb, any dereference of an RCU-protected
84 Letting RCU-protected pointers "leak" out of an RCU read-side
99 an RCU-protected list. Alternatively, use the other
100 RCU-protected data structures that have been added to
153 code know exactly which pointers are protected by RCU.
192 in their respective types of RCU-protected lists.
195 type of RCU-protected linked lists.
302 used by the RCU-protected data structure, including
348 critical section or must be protected by appropriate update-side
494 check that accesses to RCU-protected data structures
[all …]
/linux/drivers/scsi/elx/libefc/
H A Defclib.c10 * The critical sections protected by the efc's spinlock are quite broad and
15 * means that the entry points into the libefc library are protected by efc
16 * lock. So all the state machine transitions are protected.

12345678910>>...48