| /linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 2 Reliable Stacktrace
5 This document outlines basic information about reliable stacktracing.
21 to provide a *reliable* stacktrace which ensures it never omits any live
28 Architectures must implement one of the reliable stacktrace functions.
33 Principally, the reliable stacktrace function must ensure that either:
36 return code is zero to indicate that the trace is reliable.
38 * The return code is non-zero to indicate that the trace is not reliable.
45 Secondly, the reliable stacktrace function must be robust to cases where
117 which is known to be reliable to unwind from, and reject unwinding from all
136 in a consistent state suitable for reliable unwinding, but this may not be the
[all …]
|
| H A D | index.rst | 16 reliable-stacktrace
|
| /linux/arch/openrisc/kernel/ |
| H A D | unwinder.c | 41 * get reliable stack traces by matching the previously found frame
61 void (*trace)(void *data, unsigned long addr, int reliable)) in unwind_stack() argument
65 int reliable = 0; in unwind_stack() local
76 reliable = 1; in unwind_stack()
79 reliable = 0; in unwind_stack()
81 trace(data, frameinfo->ra, reliable); in unwind_stack()
94 void (*trace)(void *data, unsigned long addr, int reliable)) in unwind_stack() argument
|
| H A D | stacktrace.c | 26 save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
30 if (!reliable) in save_stack_address()
49 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
53 if (!reliable) in save_stack_address_nosched()
|
| /linux/arch/um/kernel/ |
| H A D | stacktrace.c | 20 int reliable = 0; in dump_trace() local
32 reliable = 0; in dump_trace()
36 reliable = 1; in dump_trace()
38 ops->address(data, addr, reliable); in dump_trace()
44 static void save_addr(void *data, unsigned long address, int reliable) in save_addr() argument
48 if (!reliable) in save_addr()
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 21 reliable. However, there are exceptions. In order to work with these
36 with cached value, the initial returning value is likely not reliable.
47 tested, it is reliable from all AML tables.
58 the previous explanation, it is not reliable enough on some platforms. So
81 of the _LID control method is reliable but the initial lid state
93 control method is not reliable and the initial lid state notification is
103 ensure that the reliable "closed" notifications can always be delivered
|
| /linux/arch/s390/kernel/ |
| H A D | unwind_bc.c | 60 bool reliable; in unwind_next_frame() local
67 reliable = false; in unwind_next_frame()
85 reliable = true; in unwind_next_frame()
100 reliable = true; in unwind_next_frame()
111 state->reliable = reliable; in unwind_next_frame()
168 state->reliable = true; in __unwind_start()
|
| /linux/arch/sh/kernel/ |
| H A D | stacktrace.c | 21 static void save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
25 if (!reliable) in save_stack_address()
50 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
54 if (!reliable) in save_stack_address_nosched()
|
| H A D | dumpstack.c | 47 void printk_address(unsigned long address, int reliable) in printk_address() argument
50 reliable ? "" : "? ", (void *) address); in printk_address()
113 static void print_trace_address(void *data, unsigned long addr, int reliable) in print_trace_address() argument
116 printk_address(addr, reliable); in print_trace_address()
|
| H A D | perf_callchain.c | 14 static void callchain_address(void *data, unsigned long addr, int reliable) in callchain_address() argument
18 if (reliable) in callchain_address()
|
| H A D | unwinder.c | 21 * provide. For architectures without reliable frame pointers, e.g.
146 * Hopefully this will give us a semi-reliable stacktrace so we in unwind_stack()
|
| /linux/net/rds/ |
| H A D | Kconfig | 4 tristate "The Reliable Datagram Sockets Protocol"
7 The RDS (Reliable Datagram Sockets) protocol provides reliable,
|
| /linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-edp.yaml | 91 hpd-reliable-delay-ms:
94 panel's power-supply before the HPD signal is a reliable way to know
97 always reliable for all panels that might be connected.
105 include the hpd-reliable-delay, so if hpd-reliable-delay was 80 ms
178 hpd-reliable-delay-ms = <15>;
|
| /linux/drivers/net/wan/ |
| H A D | hdlc_fr.c | 14 0,x -> 1,1 if "link reliable" when sending FULL STATUS
21 (exist,new,active) = FULL STATUS if "link reliable"
24 active = open and "link reliable"
139 int reliable; member
509 if (state(hdlc)->reliable && !pvc->state.exist) { in fr_lmi_send()
550 static void fr_set_link_state(int reliable, struct net_device *dev) in fr_set_link_state() argument
555 state(hdlc)->reliable = reliable; in fr_set_link_state()
556 if (reliable) { in fr_set_link_state()
587 int i, cnt = 0, reliable; in fr_timer() local
591 reliable = state(hdlc)->request && in fr_timer()
[all …]
|
| /linux/drivers/mtd/devices/ |
| H A D | docg3.c | 54 "2=reliable) : MLC normal operations are in normal mode");
303 * doc_set_reliable_mode - Sets the flash to normal or reliable data mode
306 * The reliable data mode is a bit slower than the fast mode, but less errors
307 * occur. Entering the reliable mode cannot be done without entering the fast
310 * In reliable mode, pages 2*n and 2*n+1 are clones. Writing to page 0 of blocks
319 static char *strmode[] = { "normal", "fast", "reliable", "invalid" }; in doc_set_reliable_mode()
321 doc_dbg("doc_set_reliable_mode(%s)\n", strmode[docg3->reliable]); in doc_set_reliable_mode()
322 switch (docg3->reliable) { in doc_set_reliable_mode()
825 * @reliable: 0 if docg3 in normal mode, 1 if docg3 in fast mode, 2 if docg3 in
826 * reliable mode.
[all …]
|
| H A D | docg3.h | 278 * @reliable: if 0, docg3 in normal mode, if 1 docg3 in fast mode, if 2 in
279 * reliable mode
281 * Reliable mode implies that page 2*n and 2*n+1 are clones.
294 unsigned int reliable:2; member
|
| /linux/drivers/acpi/ |
| H A D | button.c | 222 * On most platforms, the lid device is reliable. However in acpi_lid_notify_state()
233 * reliable. in acpi_lid_notify_state()
234 * 2. The open event may not be reliable. in acpi_lid_notify_state()
235 * 3. The close event is reliable. in acpi_lid_notify_state()
240 * platform triggered reliable event. By inserting a in acpi_lid_notify_state()
242 * platform triggered reliable one can always be seen by in acpi_lid_notify_state()
249 * as "close" is reliable and wrong "open" won't in acpi_lid_notify_state()
252 * "open" as "open" is not reliable and wrong in acpi_lid_notify_state()
262 /* Send the platform triggered reliable event */ in acpi_lid_notify_state()
|
| /linux/drivers/bluetooth/ |
| H A D | hci_bcsp.c | 45 struct sk_buff_head rel; /* Reliable packets queue */
72 /* Reliable packet sequence number - used to assign seq to each rel pkt. */
174 rel = 1; /* reliable channel */ in bcsp_prepare_pkt()
178 rel = 1; /* reliable channel */ in bcsp_prepare_pkt()
296 /* Now, try to send a reliable pkt. We can only send a in bcsp_dequeue()
297 * reliable packet if the number of packets sent but not yet ack'ed in bcsp_dequeue()
324 /* We could not send a reliable packet, either because there are in bcsp_dequeue()
479 if (bcsp->rx_skb->data[0] & 0x80) { /* reliable pkt */ in bcsp_complete_rx_pkt()
497 /* send current txack value to all received reliable packets */ in bcsp_complete_rx_pkt()
553 "reliable" : "unreliable"); in bcsp_complete_rx_pkt()
|
| /linux/arch/x86/kernel/ |
| H A D | dumpstack.c | 68 static void printk_stack_address(unsigned long address, int reliable, in printk_stack_address() argument
72 printk("%s %s%pBb\n", log_lvl, reliable ? "" : "? ", (void *)address); in printk_stack_address()
254 int reliable = 0; in show_trace_log_lvl() local
270 reliable = 1; in show_trace_log_lvl()
285 printk_stack_address(real_addr, reliable, log_lvl); in show_trace_log_lvl()
287 if (!reliable) in show_trace_log_lvl()
|
| H A D | tsc_msr.c | 227 * TSC is reliable. We were told by silicon design team that TSC in cpu_khz_from_msr()
228 * on Atom SoCs are always "reliable". TSC is also the only in cpu_khz_from_msr()
229 * reliable clocksource on these SoCs (HPET is either not present in cpu_khz_from_msr()
230 * or not functional) so mark TSC reliable which removes the in cpu_khz_from_msr()
|
| /linux/drivers/media/rc/img-ir/ |
| H A D | Kconfig | 17 less reliable (due to lack of timestamps) and consumes more
26 signals in hardware. This is more reliable, consumes less processing
|
| /linux/Documentation/networking/ |
| H A D | tcp-thin.rst | 7 A wide range of Internet-based services that use reliable transport
51 reliable transport"
|
| H A D | rds.rst | 19 RDS provides reliable, ordered datagram delivery by using a single
20 reliable connection between any two nodes in the cluster. This allows
40 reliable IB connection; the IP address is used exclusively to
101 transparently establish the underlying reliable connection
226 One might think that with reliable IB connections you wouldn't need
|
| /linux/tools/objtool/Documentation/ |
| H A D | objtool.txt | 19 stack traces are reliable for live patching
100 code and C inline assembly code so that stack traces can be reliable.
113 a) More reliable stack traces for frame pointer enabled kernels
131 For stack traces based on frame pointers to be reliable, all
182 reliable even when interrupts or exceptions are involved.
190 stack traces need to be reliable (or an unreliable condition needs to
|
| /linux/sound/firewire/oxfw/ |
| H A D | oxfw.c | 335 // field in CIP header is not reliable as synchronization timing,
342 // Behringer,F-Control Audio 202. The value of SYT field is not reliable at all.
352 // The value of SYT field in CIP header is enough reliable. Both of blocking and non-blocking
|