/Linux-v6.1/Documentation/livepatch/ |
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-v6.1/Documentation/firmware-guide/acpi/ |
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-v6.1/Documentation/devicetree/bindings/timer/ |
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-v6.1/arch/powerpc/kernel/ |
D | stacktrace.c | 60 * This function returns an error if it detects any unreliable features of the 88 * an unreliable stack trace until it's been in arch_stack_walk_reliable() 137 /* Mark stacktraces with exception frames as unreliable. */ in arch_stack_walk_reliable() 156 * as unreliable. in arch_stack_walk_reliable()
|
/Linux-v6.1/arch/arm/boot/dts/ |
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-v6.1/Documentation/admin-guide/device-mapper/ |
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-v6.1/drivers/hwmon/ |
D | k10temp.c | 310 * may be unreliable. in has_erratum_319() 383 int unreliable = has_erratum_319(pdev); in k10temp_probe() local 389 if (unreliable) { in k10temp_probe() 392 "unreliable CPU thermal sensor; monitoring disabled\n"); in k10temp_probe() 396 "unreliable CPU thermal sensor; check erratum 319\n"); in k10temp_probe()
|
/Linux-v6.1/drivers/bluetooth/ |
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-v6.1/arch/arm64/tools/ |
D | cpucaps | 8 # Unreliable: use system_supports_32bit_el0() instead.
|
/Linux-v6.1/Documentation/PCI/ |
D | pcieaer-howto.rst | 116 to be unreliable. Depending on those error conditions, uncorrectable 118 Non-fatal errors cause the particular transaction to be unreliable, 120 the other hand, cause the link to be unreliable.
|
/Linux-v6.1/net/dccp/ |
D | Kconfig | 12 congestion-controlled, unreliable datagrams. It should be suitable
|
/Linux-v6.1/drivers/ras/ |
D | Kconfig | 29 so have ideal availability, but may be unreliable, with frequent
|
/Linux-v6.1/arch/s390/kernel/ |
D | stacktrace.c | 46 * as unreliable. in arch_stack_walk_reliable()
|
/Linux-v6.1/Documentation/hwmon/ |
D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
/Linux-v6.1/drivers/misc/genwqe/ |
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-v6.1/include/uapi/linux/ |
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
|
D | parport.h | 91 #define PARPORT_EPP_FAST (1<<0) /* Unreliable counts. */
|
/Linux-v6.1/drivers/scsi/ |
D | sr.h | 49 bool ignore_get_event:1; /* GET_EVENT is unreliable, use TUR */
|
/Linux-v6.1/Documentation/admin-guide/ |
D | init.rst | 19 --> initial console unavailable. E.g. some serial consoles are unreliable
|
/Linux-v6.1/fs/isofs/ |
D | util.c | 43 * The timezone offset is unreliable on some disks, in iso_date()
|
/Linux-v6.1/kernel/ |
D | stacktrace.c | 185 * Return: An error if it detects any unreliable features of the 334 * Return: An error if it detects any unreliable features of the
|
/Linux-v6.1/kernel/livepatch/ |
D | transition.c | 287 * if the stack is unreliable, return false. 320 pr_debug("%s: %s:%d has an unreliable stack\n", in klp_try_switch_task() 397 * is deemed unreliable, the task can't be switched yet. in klp_try_complete_transition()
|
/Linux-v6.1/include/clocksource/ |
D | hyperv_timer.h | 48 * A special '0' value indicates the time source is unreliable and we in hv_read_tsc_page_tsc()
|
/Linux-v6.1/arch/x86/kernel/ |
D | stacktrace.c | 53 * unreliable. in arch_stack_walk_reliable()
|
/Linux-v6.1/net/sunrpc/ |
D | timer.c | 97 * Estimate RTO for an NFS RPC sent via an unreliable datagram. Use
|