Searched full:protected (Results 1 – 25 of 130) sorted by relevance
123456
| /Documentation/virt/kvm/ |
| D | s390-pv-boot.rst | 4 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.
|
| D | s390-pv.rst | 4 s390 (IBM Z) Ultravisor and Protected VMs
9 Protected virtual machines (PVM) are KVM VMs that do not allow KVM to
15 Each guest starts in non-protected mode and then may make a request to
16 transition into protected mode. On transition, KVM registers the guest
|
| D | mmu.rst | 110 - access to missing or protected translations
256 emulations if the page needs to be write-protected (see "Synchronized
278 protected, and synchronize sptes to gptes when a gpte is written.
302 - access to a protected translation
303 - when logging dirty pages, memory is write protected
304 - synchronized shadow pages are write protected (*)
430 write-protected pages
434 arrays for each memory slot and large page size. Every write protected page
|
| /Documentation/pcmcia/ |
| D | locking.rst | 62 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
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,gcc-qcs404.yaml | 33 protected-clocks:
35 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-ipq8074.yaml | 33 protected-clocks:
35 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-sm8150.yaml | 46 protected-clocks:
48 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-sm8250.yaml | 46 protected-clocks:
48 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-sc7180.yaml | 48 protected-clocks:
50 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-msm8996.yaml | 64 protected-clocks:
66 Protected clock specifier list as per common clock binding.
|
| D | qcom,gcc-msm8998.yaml | 56 protected-clocks:
58 Protected clock specifier list as per common clock binding.
|
| D | qcom,mmcc.yaml | 66 protected-clocks:
68 Protected clock specifier list as per common clock binding
|
| D | qcom,gcc-apq8064.yaml | 57 protected-clocks:
59 Protected clock specifier list as per common clock binding.
|
| D | clock-bindings.txt | 172 ==Protected clocks==
177 protected-clocks property in the form of a clock specifier list. This property should
178 only be specified in the node that is providing the clocks being protected:
185 protected-clocks = <UART3_CLK>, <SPI5_CLK>;
|
| D | qcom,gcc.yaml | 69 protected-clocks:
71 Protected clock specifier list as per common clock binding.
|
| /Documentation/RCU/ |
| D | arrayRCU.rst | 15 Each of these three situations involves an RCU-protected pointer to an
18 case is **not** supported. The problem with RCU-protected indexes into
21 are far more trouble than they are worth. If RCU-protected indexes into
26 That aside, each of the three RCU-protected pointer situations are
35 has a linked-list hash chain. Each hash chain can be protected by RCU
|
| D | checklist.rst | 66 As a rough rule of thumb, any dereference of an RCU-protected
72 Letting RCU-protected pointers "leak" out of an RCU read-side
87 an RCU-protected list. Alternatively, use the other
88 RCU-protected data structures that have been added to
138 code know exactly which pointers are protected by RCU.
178 in their respective types of RCU-protected lists.
181 type of RCU-protected linked lists.
260 used by the RCU-protected data structure, including
304 critical section or must be protected by appropriate update-side
419 check that accesses to RCU-protected data
[all …]
|
| D | rcu_dereference.rst | 15 to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
123 RCU-protected circular linked lists.
378 on the one hand, or protected by (say) my_lock on the other,
386 on the one hand, or protected by either my_lock or your_lock on
393 4. If the access is on the update side, so that it is always protected
418 SPARSE CHECKING OF RCU-PROTECTED POINTERS
421 The sparse static-analysis tool checks for direct access to RCU-protected
|
| /Documentation/filesystems/ |
| D | files.rst | 10 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
|
| /Documentation/locking/ |
| D | preempt-locking.rst | 40 RULE #2: CPU state must be protected.
44 Under preemption, the state of the CPU must be protected. This is arch-
140 is done. They may also be called within a spin-lock protected region, however,
143 are also protected by preemption locks and so may use the versions which do
|
| D | seqlock.rst | 33 This mechanism cannot be used if the protected data contains pointers,
105 that it is properly protected.
149 between two copies of protected data. This allows the sequence counter
152 Use seqcount_latch_t when the write side sections cannot be protected
|
| /Documentation/hwmon/ |
| D | max20730.rst | 67 write protected; read-write otherwise.
78 degrees C. Read-only if the chip is write protected;
|
| /Documentation/fb/ |
| D | vesafb.rst | 12 graphics mode. Switching mode later on (in protected mode) is
114 The VESA BIOS provides protected mode interface for changing
129 ypan enable display panning using the VESA protected mode
155 pmipal Use the protected mode interface for palette changes.
|
| /Documentation/x86/ |
| D | booting-dt.rst | 8 entry point once it switched into protected mode). That entry point
|
| /Documentation/ABI/testing/ |
| D | evm | 25 2 Permit modification of EVM-protected metadata at
49 modification of EVM-protected metadata and
|
123456