| /Linux-v4.19/tools/testing/radix-tree/ |
| D | multiorder.c | 397 assert(node->exceptional == 1); in multiorder_join2()
405 assert(node->exceptional == 0); in multiorder_join2()
437 assert(node->exceptional == node->count); in multiorder_join3()
524 assert(node->exceptional > 0); in __multiorder_split2()
534 assert(node->exceptional == 0); in __multiorder_split2()
551 assert(node->exceptional > 0); in __multiorder_split3()
560 assert(node->exceptional > 0); in __multiorder_split3()
568 assert(node->exceptional > 0); in __multiorder_split3()
581 assert(node->count == node->exceptional); in __multiorder_split3()
587 assert(node->exceptional == 0); in __multiorder_split3()
[all …]
|
| /Linux-v4.19/mm/ |
| D | workingset.c | 353 if (node->count && node->count == node->exceptional) { in workingset_update_node()
450 if (WARN_ON_ONCE(!node->exceptional)) in shadow_lru_isolate()
452 if (WARN_ON_ONCE(node->count != node->exceptional)) in shadow_lru_isolate()
458 if (WARN_ON_ONCE(!node->exceptional)) in shadow_lru_isolate()
463 node->exceptional--; in shadow_lru_isolate()
468 if (WARN_ON_ONCE(node->exceptional)) in shadow_lru_isolate()
|
| /Linux-v4.19/lib/ |
| D | radix-tree.c | 289 node->shift, node->count, node->exceptional); in dump_node()
381 unsigned int count, unsigned int exceptional) in radix_tree_node_alloc() argument
428 ret->exceptional = exceptional; in radix_tree_node_alloc()
661 node->exceptional = 1; in radix_tree_extend()
951 node->exceptional--; in insert_entries()
956 node->exceptional += n; in insert_entries()
970 node->exceptional++; in insert_entries()
1104 void __rcu **slot, int count, int exceptional) in replace_sibling_entries() argument
1117 node->exceptional += exceptional; in replace_sibling_entries()
1124 struct radix_tree_node *node, int count, int exceptional) in replace_slot() argument
[all …]
|
| /Linux-v4.19/arch/m68k/fpsp040/ |
| D | kernel_ex.S | 5 | fpu for exceptional cases detected or reported within the
8 | The bits are tested in gen_except.sa to determine if an exceptional
133 | On entry, a0 points to the exceptional operand. The final exceptional
138 clrl FP_SCR1(%a6) |set exceptional operand to zero
|
| D | bugfix.S | 250 | was exceptional, and was completed by the appropriate handler.
251 | If the result of the xu instruction is not exceptional, we can
254 | exceptional, we choose to kill the process.
275 | Check if the instruction which just completed was exceptional.
372 | was exceptional, and was completed by the appropriate handler.
373 | If the result of the xu instruction is not exceptional, we can
376 | exceptional, we choose to kill the process.
401 | Check if the instruction which just completed was exceptional.
|
| D | gen_except.S | 11 | the stack frame in memory with the exceptional operand(s).
254 | The exceptional operand is in FP_SCR1.
261 | caller set CU_ONLY. If so, the exceptional operand is expected in
298 movel FP_SCR1+4(%a6),WBTEMP_HI(%a6) |exceptional op to
356 movel FP_SCR1+4(%a6),WBTEMP_HI(%a1) |exceptional op to
|
| D | x_ovfl.S | 29 | All trap disabled code applies. In addition the exceptional
|
| D | x_unfl.S | 16 | All trap disabled code applies. In addition the exceptional
151 | If the exception bit set is E3, the exceptional operand from the
|
| D | x_operr.S | 305 | frame on the stack and the fpu in the original exceptional state
|
| D | decbin.S | 20 | Expected is a normal bcd (i.e. non-exceptional; all inf, zero,
|
| /Linux-v4.19/include/linux/ |
| D | radix-tree.h | 96 unsigned char exceptional; /* Exceptional entry count */ member
|
| /Linux-v4.19/Documentation/acpi/ |
| D | acpi-lid.txt | 17 exceptional buggy platforms, special restrictions and expections should be
|
| /Linux-v4.19/Documentation/devicetree/bindings/mtd/ |
| D | brcm,brcmnand.txt | 66 properties in the main controller node. But for the latter exceptional cases,
|
| /Linux-v4.19/drivers/cpufreq/ |
| D | Kconfig.x86 | 227 This driver should be only used in exceptional
|
| /Linux-v4.19/Documentation/ |
| D | this_cpu_ops.txt | 38 exceptional situations and may impact performance and/or correctness
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | libata.rst | 309 and other exceptional conditions. The primary responsibility of an
647 The term 'exception' is either used to describe exceptional conditions
649 errors and non-error exceptional conditions. Where explicit distinction
|
| /Linux-v4.19/Documentation/power/ |
| D | opp.txt | 64 factors. Example usage: Thermal management or other exceptional situations where
|
| /Linux-v4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 23 GPIO properties can contain one or more GPIO phandles, but only in exceptional
|
| /Linux-v4.19/Documentation/process/ |
| D | coding-style.rst | 374 exceptional circumstances.
|
| /Linux-v4.19/arch/m68k/ifpsp060/src/ |
| D | fpsp.S | 970 # the exceptional possibilities we have left ourselves with are ONLY overflow
4247 frestore FP_SRC(%a6) # insert exceptional status
11660 # exceptional operand.
11771 # exceptional operand.
|
| D | pfpsp.S | 969 # the exceptional possibilities we have left ourselves with are ONLY overflow
|
