/linux/Documentation/livepatch/ |
H A D | reliable-stacktrace.rst | 46 the stack or other unwind state is corrupt or otherwise unreliable. The 125 unreliable to unwind from, e.g. 151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions 176 unwinder must report these cases as unreliable. 221 middle of return_to_handler and can report this as unreliable. Architectures 250 such cases, or report the unwinding as unreliable. 263 assumption can lead to unreliable stack traces. For example, consider the
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | acpi-lid.rst | 70 If the userspace hasn't been prepared to ignore the unreliable "opened" 71 events and the unreliable initial state notification, Linux users can use 96 If the userspace has been prepared to ignore the unreliable "opened" events 97 and the unreliable initial state notification, Linux users should always
|
/linux/Documentation/devicetree/bindings/timer/ |
H A D | arm,arch_timer.yaml | 74 where reading certain values from the counter is unreliable. This also 80 that reading the counter is unreliable unless the same value is returned 87 says that reading the counters is unreliable in some cases, and reads may
|
/linux/arch/arm/boot/dts/ti/omap/ |
H A D | omap3-beagle-ab4.dts | 16 /* Unusable as clocksource because of unreliable oscillator */ 21 /* Unusable as clockevent because of unreliable oscillator, allow to idle */
|
/linux/arch/powerpc/kernel/ |
H A D | stacktrace.c | 61 * This function returns an error if it detects any unreliable features of the 121 /* Mark stacktraces with exception frames as unreliable. */ in arch_stack_walk_reliable() 140 * as unreliable. in arch_stack_walk_reliable()
|
/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-flakey.rst | 6 unreliable behaviour periodically. It's been found useful in simulating 10 <up interval> seconds, then exhibits unreliable behaviour for <down
|
/linux/drivers/bluetooth/ |
H A D | hci_bcsp.c | 46 struct sk_buff_head unrel; /* Unreliable packets queue */ 182 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt() 186 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt() 190 rel = 0; /* unreliable channel */ in bcsp_prepare_pkt() 277 /* First of all, check for unreliable messages in the queue, in bcsp_dequeue() 330 /* if so, craft an empty ACK pkt and send it on BCSP unreliable in bcsp_dequeue() 553 "reliable" : "unreliable"); in bcsp_complete_rx_pkt()
|
/linux/drivers/hwmon/ |
H A D | k10temp.c | 330 * may be unreliable. in has_erratum_319() 413 int unreliable = has_erratum_319(pdev); in k10temp_probe() local 419 if (unreliable) { in k10temp_probe() 422 "unreliable CPU thermal sensor; monitoring disabled\n"); in k10temp_probe() 426 "unreliable CPU thermal sensor; check erratum 319\n"); in k10temp_probe()
|
/linux/net/dccp/ |
H A D | Kconfig | 12 congestion-controlled, unreliable datagrams. It should be suitable
|
/linux/drivers/misc/genwqe/ |
H A D | card_sysfs.c | 137 * unreliable data in very rare cases. This makes this sysfs 138 * unreliable up to the point were a new CPLD version is being used.
|
/linux/drivers/ras/ |
H A D | Kconfig | 29 so have ideal availability, but may be unreliable, with frequent
|
/linux/Documentation/hwmon/ |
H A D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
/linux/include/linux/ |
H A D | objtool_types.h | 25 * a truncated and unreliable stack unwind.
|
/linux/tools/include/linux/ |
H A D | objtool_types.h | 25 * a truncated and unreliable stack unwind.
|
/linux/include/uapi/linux/ |
H A D | virtio_ring.h | 55 * you add a buffer. It's unreliable, so it's simply an optimization. Guest 59 * when you consume a buffer. It's unreliable, so it's simply an
|
H A D | parport.h | 91 #define PARPORT_EPP_FAST (1<<0) /* Unreliable counts. */
|
/linux/kernel/ |
H A D | stacktrace.c | 186 * Return: An error if it detects any unreliable features of the 336 * Return: An error if it detects any unreliable features of the
|
/linux/Documentation/admin-guide/ |
H A D | init.rst | 19 --> initial console unavailable. E.g. some serial consoles are unreliable
|
/linux/fs/isofs/ |
H A D | util.c | 43 * The timezone offset is unreliable on some disks, in iso_date()
|
/linux/drivers/firmware/arm_scmi/ |
H A D | Kconfig | 56 SCMI Raw mode support unreliable. If unsure, say N.
|
/linux/arch/x86/kernel/ |
H A D | stacktrace.c | 53 * unreliable. in arch_stack_walk_reliable()
|
H A D | dumpstack.c | 278 * address as an "unreliable" hint that function graph in show_trace_log_lvl() 294 * of the addresses will just be printed as unreliable. in show_trace_log_lvl()
|
/linux/include/clocksource/ |
H A D | hyperv_timer.h | 55 * A special '0' value indicates the time source is unreliable and we in hv_read_tsc_page_tsc()
|
/linux/kernel/livepatch/ |
H A D | transition.c | 312 * if the stack is unreliable, return false. 349 pr_debug("%s: %s:%d has an unreliable stack\n", in klp_try_switch_task() 464 * is deemed unreliable, the task can't be switched yet. in klp_try_complete_transition()
|
/linux/net/sunrpc/ |
H A D | timer.c | 97 * Estimate RTO for an NFS RPC sent via an unreliable datagram. Use
|