Searched full:exceptional (Results 1 – 25 of 69) sorted by relevance
123
| /linux-6.14.4/arch/m68k/fpsp040/ |
| D | bugfix.S | 65 | /* If the xu instruction is exceptional, we punt.
114 | /* If the xu instruction is exceptional, we punt.
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 | 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
226 clrl FP_SCR1(%a6) |set exceptional operand
247 bsetb #sign_bit,FP_SCR1(%a6) |set exceptional operand sign
|
| D | scale.S | 232 | t_resdnrm with exceptional operand in ETEMP.
283 clrl FP_SCR1(%a6) |clear the exceptional operand
289 clrl FP_SCR1(%a6) |clear the exceptional operand
334 | exceptional operand in ETEMP.
|
| 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_operr.S | 39 | The exceptional operand is not defined for integer overflow
95 | fpu in the original exceptional state.
305 | frame on the stack and the fpu in the original exceptional state
|
| 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_ovfl.S | 29 | All trap disabled code applies. In addition the exceptional
|
| /linux-6.14.4/include/linux/ |
| D | pagevec.h | 25 * folio_batch store "exceptional" entries in it which can be removed
|
| /linux-6.14.4/drivers/extcon/ |
| D | extcon.h | 38 * this struct when registering an extcon. In some exceptional cases,
|
| /linux-6.14.4/arch/parisc/math-emu/ |
| D | sfcmp.c | 74 /* All the exceptional conditions are handled, now special case in sgl_fcmp()
|
| D | dfcmp.c | 74 /* All the exceptional conditions are handled, now special case in dbl_fcmp()
|
| /linux-6.14.4/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | frontend.json | 70 …so be delivered in response to some condition such as a fault or other exceptional condition. Thi…
|
| /linux-6.14.4/arch/m68k/ifpsp060/ |
| D | fskeleton.S | 73 | stack frame. The FP state frame holds the EXCEPTIONAL OPERAND.
92 | stack frame. The FP state frame holds the EXCEPTIONAL OPERAND.
|
| /linux-6.14.4/Documentation/process/ |
| D | security-bugs.rst | 48 of the release process, with an exceptional extension to 14 calendar days
|
| /linux-6.14.4/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 22 exceptional buggy platforms, special restrictions and exceptions should be
|
| /linux-6.14.4/arch/x86/boot/ |
| D | video-mode.c | 98 /* Nothing found? Is it an "exceptional" (unprobed) mode? */ in raw_set_mode()
|
| /linux-6.14.4/arch/mips/kernel/ |
| D | sync-r4k.c | 34 * We use a raw spinlock in this exceptional case, because
|
| /linux-6.14.4/lib/ |
| D | test_ida.c | 125 * Check handling of conversions between exceptional entries and full bitmaps.
|
| /linux-6.14.4/Documentation/devicetree/bindings/mtd/ |
| D | brcm,brcmnand.yaml | 38 exceptional cases, we define additional 'compatible' properties and associated
|
| /linux-6.14.4/drivers/cpufreq/ |
| D | Kconfig.x86 | 270 This driver should be only used in exceptional
|
| /linux-6.14.4/Documentation/driver-api/ |
| D | libata.rst | 285 and other exceptional conditions. The primary responsibility of an
610 The term 'exception' is either used to describe exceptional conditions
612 errors and non-error exceptional conditions. Where explicit distinction
|
| /linux-6.14.4/Documentation/core-api/ |
| D | this_cpu_ops.rst | 38 exceptional situations and may impact performance and/or correctness
|
| /linux-6.14.4/fs/vboxsf/ |
| D | vboxsf_wrappers.c | 120 * Note this function always returns 0 / success unless an exceptional condition
|
| /linux-6.14.4/mm/ |
| D | truncate.c | 54 * Unconditionally remove exceptional entries. Usually called from truncate
56 * exceptional entries similar to what folio_batch_remove_exceptionals() does.
|
| /linux-6.14.4/Documentation/networking/ |
| D | udplite.rst | 235 Exceptional and error conditions are logged to syslog at the KERN_DEBUG
|
123