| /linux-6.1.9/mm/ |
| D | page_counter.c | 19 unsigned long protected, old_protected; in propagate_protected_usage() local
25 protected = min(usage, READ_ONCE(c->min)); in propagate_protected_usage()
27 if (protected != old_protected) { in propagate_protected_usage()
28 old_protected = atomic_long_xchg(&c->min_usage, protected); in propagate_protected_usage()
29 delta = protected - old_protected; in propagate_protected_usage()
34 protected = min(usage, READ_ONCE(c->low)); in propagate_protected_usage()
36 if (protected != old_protected) { in propagate_protected_usage()
37 old_protected = atomic_long_xchg(&c->low_usage, protected); in propagate_protected_usage()
38 delta = protected - old_protected; in propagate_protected_usage()
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/mm/ |
| D | arch_pgtable_helpers.rst | 53 | pte_wrprotect | Creates a write protected PTE |
77 | ptep_set_wrprotect | Converts into a write protected PTE |
125 | pmd_wrprotect | Creates a write protected PMD |
151 | pmdp_set_wrprotect | Converts into a write protected PMD |
191 | pud_wrprotect | Creates a write protected PUD |
207 | pudp_set_wrprotect | Converts into a write protected PUD |
229 | huge_pte_wrprotect | Creates a write protected HugeTLB |
233 | huge_ptep_set_wrprotect | Converts into a write protected HugeTLB |
|
| /linux-6.1.9/Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
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 | 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
|
| /linux-6.1.9/arch/x86/realmode/rm/ |
| D | trampoline_32.S | 53 movw $1, %dx # protected mode (PE) bit
54 lmsw %dx # into protected mode
|
| D | trampoline_64.S | 72 # Enable protected mode
74 movl %eax, %cr0 # into protected mode
|
| /linux-6.1.9/tools/testing/selftests/cgroup/ |
| D | memcg_protection.m | 51 protected = min(n, c); % start with nominal variable
52 e = protected * min(1, E / siblings); % normalize overcommit
58 overuse = max(0, c - protected);
|
| /linux-6.1.9/scripts/kconfig/ |
| D | qconf.h | 56 protected:
204 protected:
227 protected:
262 protected:
|
| /linux-6.1.9/drivers/mtd/spi-nor/ |
| D | Kconfig | 47 power-up or a reset the flash is software write protected by
65 protected or will be automatically software write protected after
|
| /linux-6.1.9/arch/powerpc/boot/dts/ |
| D | mpc5121ads.dts | 39 protected@0 {
40 label = "protected";
41 reg = <0x00000000 0x00040000>; // first sector is protected
|
| /linux-6.1.9/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
77 Letting RCU-protected pointers "leak" out of an RCU read-side
92 an RCU-protected list. Alternatively, use the other
93 RCU-protected data structures that have been added to
141 code know exactly which pointers are protected by RCU.
180 in their respective types of RCU-protected lists.
183 type of RCU-protected linked lists.
278 used by the RCU-protected data structure, including
323 critical section or must be protected by appropriate update-side
445 check that accesses to RCU-protected data
[all …]
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/hwmon/ |
| D | max20730.rst | 67 write protected; read-write otherwise.
78 degrees C. Read-only if the chip is write protected;
|
| /linux-6.1.9/arch/arm64/kvm/ |
| D | Kconfig | 66 If using protected nVHE mode, but cannot afford the associated
70 If unsure, or not using protected nVHE (pKVM), say N.
|
| /linux-6.1.9/drivers/clk/sunxi/ |
| D | clk-simple-gates.c | 19 const int protected[], in sunxi_simple_gates_setup() argument
70 if (protected[j] == index) in sunxi_simple_gates_setup()
|
| /linux-6.1.9/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
|
| /linux-6.1.9/arch/powerpc/sysdev/ |
| D | mpic.c | 1012 if (mpic->protected && test_bit(hw, mpic->protected)) { in mpic_host_map()
1328 mpic->protected = bitmap_zalloc(intvec_top + 1, GFP_KERNEL); in mpic_alloc()
1329 BUG_ON(mpic->protected == NULL); in mpic_alloc()
1333 __set_bit(psrc[i], mpic->protected); in mpic_alloc()
1614 if (mpic->protected && test_bit(i, mpic->protected)) in mpic_init()
1781 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in _mpic_get_one_irq()
1820 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in mpic_get_coreint_irq()
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/tools/memory-model/litmus-tests/ |
| D | MP+onceassign+derefonce.litmus | 8 * pre-initialization garbage when it traverses an RCU-protected data
|
| D | MP+unlocklockonceonce+fencermbonceonce.litmus | 8 * the critical sections are protected by different locks.
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-thermocouple | 6 is protected from excessive voltages applied to the thermocouple
|
| /linux-6.1.9/Documentation/devicetree/bindings/clock/ |
| D | qcom,gcc.yaml | 30 protected-clocks:
|