| /Linux-v4.19/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-v4.19/Documentation/pcmcia/ |
| D | locking.txt | 53 protected by pcmcia_socket_list_rwsem;
58 The resource_ops and their data are protected by ops_mutex.
60 The "main" struct pcmcia_socket is protected as follows (read-only fields
99 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /Linux-v4.19/scripts/kconfig/ |
| D | qconf.h | 54 protected:
257 protected:
281 protected:
314 protected:
|
| /Linux-v4.19/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.
259 used by the RCU-protected data structure, including
308 critical section or must be protected by appropriate update-side
328 all currently executing rcu_read_lock()-protected RCU read-side
[all …]
|
| D | rcuref.txt | 1 Reference-count design for elements of lists/arrays protected by RCU.
12 Reference counting on elements of lists which are protected by traditional
|
| D | 00-INDEX | 22 - Reference-count design for elements of lists/arrays protected by RCU
|
| D | lockdep-splat.txt | 4 family to access an RCU-protected pointer without the proper protection.
8 RCU-protected data structure without either (1) being in the right kind of
|
| /Linux-v4.19/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-v4.19/arch/powerpc/boot/dts/ |
| D | mpc5121ads.dts | 43 protected@0 {
44 label = "protected";
45 reg = <0x00000000 0x00040000>; // first sector is protected
|
| /Linux-v4.19/drivers/clk/sunxi/ |
| D | clk-simple-gates.c | 27 const int protected[], in sunxi_simple_gates_setup() argument
78 if (protected[j] == index) in sunxi_simple_gates_setup()
|
| /Linux-v4.19/Documentation/ |
| D | preempt-locking.txt | 41 RULE #2: CPU state must be protected.
45 Under preemption, the state of the CPU must be protected. This is arch-
141 is done. They may also be called within a spin-lock protected region, however,
144 are also protected by preemption locks and so may use the versions which do
|
| /Linux-v4.19/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-v4.19/tools/memory-model/litmus-tests/ |
| D | MP+onceassign+derefonce.litmus | 8 * pre-initialization garbage when it traverses an RCU-protected data
|
| D | ISA2+pooncelock+pooncelock+pombonce.litmus | 6 * This test shows that the ordering provided by a lock-protected S
|
| D | README | 37 Tests whether the ordering provided by a lock-protected S
79 and the first access of reader process protected by a lock.
89 and the second access of reader process protected by a lock.
|
| /Linux-v4.19/Documentation/fb/ |
| D | vesafb.txt | 12 graphics mode. Switching mode later on (in protected mode) is
109 The VESA BIOS provides protected mode interface for changing
123 ypan enable display panning using the VESA protected mode
145 pmipal Use the protected mode interface for palette changes.
|
| D | uvesafb.txt | 60 ypan Enable display panning using the VESA protected mode
79 pmipal Use the protected mode interface for palette changes.
80 This is the default if the protected mode interface is
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | evm | 23 2 Permit modification of EVM-protected metadata at
42 modification of EVM-protected metadata and
|
| /Linux-v4.19/arch/powerpc/kernel/vdso64/ |
| D | datapage.S | 28 .protected __get_datapage
|
| /Linux-v4.19/arch/powerpc/kernel/vdso32/ |
| D | datapage.S | 28 .protected __get_datapage
|
| /Linux-v4.19/Documentation/vm/ |
| 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.
|
| 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
|
| /Linux-v4.19/arch/powerpc/boot/dts/fsl/ |
| D | p1020rdb-pc_camp_core0.dts | 57 protected-sources = <
|
| D | mpc8572ds_camp_core0.dts | 60 protected-sources = <
|
