Searched full:protected (Results 1 – 25 of 161) sorted by relevance
1234567
| /Documentation/virt/kvm/arm/ |
| D | pkvm.rst | 3 Protected virtual machines (pKVM)
9 Protected KVM (pKVM) is a KVM/arm64 extension which uses the two-stage
29 "``kvm-arm.mode=protected``" on the command-line. Once enabled, VMs can be spawned
30 in either protected or non-protected state, although the hypervisor is still
37 whether they are spawned in protected state. It is therefore recommended only
38 to enable pKVM if protected VMs are required, with non-protected state acting
70 When pKVM is enabled, protected VMs can be created by specifying the
74 Protected VMs are instantiated according to a fixed vCPU configuration
82 Where not defined by the architecture, the registers of a protected vCPU
89 By default, memory pages mapped into a protected guest are inaccessible to the
[all …]
|
| /Documentation/virt/kvm/s390/ |
| 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-dump.rst | 4 s390 (IBM Z) Protected Virtualization dumps
11 it. This is especially true when a protected VM runs into trouble as
15 However when dumping a protected VM we need to maintain its
|
| 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
|
| /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.yaml | 30 protected-clocks:
32 Protected clock specifier list as per common clock binding.
|
| /Documentation/gpu/xe/ |
| D | xe_firmware.rst | 16 Write Once Protected Content Memory (WOPCM) Layout
20 :doc: Write Once Protected Content Memory (WOPCM) Layout
|
| /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/RCU/ |
| D | checklist.rst | 66 As a rough rule of thumb, any dereference of an RCU-protected
78 Letting RCU-protected pointers "leak" out of an RCU read-side
93 an RCU-protected list. Alternatively, use the other
94 RCU-protected data structures that have been added to
147 code know exactly which pointers are protected by RCU.
186 in their respective types of RCU-protected lists.
189 type of RCU-protected linked lists.
296 used by the RCU-protected data structure, including
342 critical section or must be protected by appropriate update-side
481 check that accesses to RCU-protected data structures
[all …]
|
| D | rcu_dereference.rst | 28 to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
143 RCU-protected circular linked lists.
417 on the one hand, or protected by (say) my_lock on the other,
425 on the one hand, or protected by either my_lock or your_lock on
432 4. If the access is on the update side, so that it is always protected
457 SPARSE CHECKING OF RCU-PROTECTED POINTERS
460 The sparse static-analysis tool checks for non-RCU access to RCU-protected
|
| D | whatisRCU.rst | 169 can preempt RCU read-side critical sections. Any RCU-protected
259 RCU-protected pointer, in order to safely communicate the change
270 (1) which pointers are protected by RCU and (2) the point at which
283 an RCU-protected pointer, which returns a value that may
297 RCU-protected pointer to a local variable, then dereferences
309 RCU-protected structure, using the local variable is of
335 rcu_dereference() is to document which pointers are protected by
344 protected by locks acquired by the update-side code. This variant
394 spatial changes via stores to and loads from the RCU-protected pointer in
503 to dereference RCU-protected pointers.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-thermocouple | 6 is protected from excessive voltages applied to the thermocouple
|
| D | sysfs-driver-ccp | 50 whether Replay Protected Monotonic Counter support has been enabled.
61 whether an Replay Protected Monotonic Counter supported SPI is installed
|
| D | evm | 26 2 Permit modification of EVM-protected metadata at
50 modification of EVM-protected metadata and
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 70 management for the protected VMs. The capability is mainly about the lifecycle
73 under proper security measures required by protected VMs.
|
| /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/arch/x86/ |
| D | booting-dt.rst | 8 entry point once it switched into protected mode). That entry point
|
| /Documentation/virt/kvm/x86/ |
| D | mmu.rst | 110 - access to missing or protected translations
278 emulations if the page needs to be write-protected (see "Synchronized
304 protected, and synchronize sptes to gptes when a gpte is written.
328 - access to a protected translation
329 - when logging dirty pages, memory is write protected
330 - synchronized shadow pages are write protected (*)
456 write-protected pages
460 arrays for each memory slot and large page size. Every write protected page
|
| /Documentation/devicetree/bindings/iommu/ |
| D | pkvm,pviommu.yaml | 15 pvIOMMU was initially developed for protected KVM (pKVM), but it has no
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | qcom,sec-qfprom.yaml | 14 protected from non-secure access. In such situations, the OS have to use
|
| /Documentation/mm/ |
| D | split_page_table_lock.rst | 5 Originally, mm->page_table_lock spinlock protected all page tables of the
12 tables. Access to higher level tables protected by mm->page_table_lock.
|
| /Documentation/admin-guide/mm/ |
| D | pagemap.rst | 22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
222 non-Async Write Protected pages are found. The ``PM_SCAN_WP_MATCHING`` can be
230 - ``PAGE_IS_WRITTEN`` - Page has been written to from the time it was write protected
294 be write protected using ``PAGEMAP_SCAN`` IOCTL with flag ``PM_SCAN_WP_MATCHING``
|
1234567