| /Linux-v5.4/mm/ |
| D | page_counter.c | 19 unsigned long protected, old_protected; in propagate_protected_usage() local
27 protected = usage; in propagate_protected_usage()
29 protected = 0; in propagate_protected_usage()
31 old_protected = atomic_long_xchg(&c->min_usage, protected); in propagate_protected_usage()
32 delta = protected - old_protected; in propagate_protected_usage()
39 protected = usage; in propagate_protected_usage()
41 protected = 0; in propagate_protected_usage()
43 old_protected = atomic_long_xchg(&c->low_usage, protected); in propagate_protected_usage()
44 delta = protected - old_protected; in propagate_protected_usage()
|
| /Linux-v5.4/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-v5.4/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 | 71 # Enable protected mode
72 movl $X86_CR0_PE, %eax # protected mode (PE) bit
73 movl %eax, %cr0 # into protected mode
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | qcom,gcc.txt | 39 - protected-clocks : Protected clock specifier list as per common clock
69 Example of GCC with protected-clocks properties:
76 protected-clocks = <GCC_QSPI_CORE_CLK>,
|
| D | clock-bindings.txt | 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>;
|
| /Linux-v5.4/scripts/kconfig/ |
| D | qconf.h | 54 protected:
257 protected:
281 protected:
315 protected:
|
| /Linux-v5.4/Documentation/RCU/ |
| D | arrayRCU.txt | 13 Each of these three situations involves an RCU-protected pointer to an
16 case is -not- supported. The problem with RCU-protected indexes into
19 are far more trouble than they are worth. If RCU-protected indexes into
24 That aside, each of the three RCU-protected pointer situations are
31 has a linked-list hash chain. Each hash chain can be protected by RCU
|
| D | checklist.txt | 62 As a rough rule of thumb, any dereference of an RCU-protected
68 Letting RCU-protected pointers "leak" out of an RCU read-side
83 an RCU-protected list. Alternatively, use the other
84 RCU-protected data structures that have been added to
134 code know exactly which pointers are protected by RCU.
174 in their respective types of RCU-protected lists.
177 type of RCU-protected linked lists.
256 used by the RCU-protected data structure, including
300 critical section or must be protected by appropriate update-side
414 CONFIG_PROVE_LOCKING: check that accesses to RCU-protected data
[all …]
|
| /Linux-v5.4/arch/powerpc/boot/dts/ |
| D | mpc5121ads.dts | 39 protected@0 {
40 label = "protected";
41 reg = <0x00000000 0x00040000>; // first sector is protected
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | files.txt | 7 Up until 2.6.12, the file descriptor table has been protected
9 ->file_lock protected accesses to all the file related fields
15 The files (struct file) themselves are protected using
55 2. Reading of the fdtable as described above must be protected
|
| /Linux-v5.4/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-v5.4/Documentation/ |
| D | preempt-locking.txt | 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
|
| /Linux-v5.4/arch/powerpc/sysdev/ |
| D | mpic.c | 1010 if (mpic->protected && test_bit(hw, mpic->protected)) { in mpic_host_map()
1327 mpic->protected = kcalloc(mapsize, sizeof(long), GFP_KERNEL); in mpic_alloc()
1328 BUG_ON(mpic->protected == NULL); in mpic_alloc()
1332 __set_bit(psrc[i], mpic->protected); in mpic_alloc()
1615 if (mpic->protected && test_bit(i, mpic->protected)) in mpic_init()
1782 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in _mpic_get_one_irq()
1821 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in mpic_get_coreint_irq()
|
| /Linux-v5.4/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
157 pmipal Use the protected mode interface for palette changes.
|
| D | uvesafb.rst | 61 ypan Enable display panning using the VESA protected mode
82 pmipal Use the protected mode interface for palette changes.
83 This is the default if the protected mode interface is
|
| /Linux-v5.4/tools/memory-model/litmus-tests/ |
| D | MP+onceassign+derefonce.litmus | 8 * pre-initialization garbage when it traverses an RCU-protected data
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | evm | 23 2 Permit modification of EVM-protected metadata at
42 modification of EVM-protected metadata and
|
| D | sysfs-bus-iio-temperature-max31856 | 17 is protected from excessive voltages applied to the thermocouple
|
| /Linux-v5.4/arch/powerpc/kernel/vdso64/ |
| D | datapage.S | 24 .protected __get_datapage
|
| /Linux-v5.4/arch/powerpc/kernel/vdso32/ |
| D | datapage.S | 24 .protected __get_datapage
|
| /Linux-v5.4/arch/powerpc/boot/dts/fsl/ |
| D | mpc8572ds_camp_core0.dts | 56 protected-sources = <
|
| D | p1020rdb-pc_camp_core0.dts | 53 protected-sources = <
|
| /Linux-v5.4/Documentation/vm/ |
| D | mmu_notifier.rst | 36 they are write protected for COW (other case of B apply too).
95 When changing a pte to write protect or to point to a new write protected page
|
| D | split_page_table_lock.rst | 7 Originally, mm->page_table_lock spinlock protected all page tables of the
14 tables. Access to higher level tables protected by mm->page_table_lock.
|
