| /Linux-v5.4/arch/s390/kernel/ |
| D | unwind_bc.c | 45 bool reliable; in unwind_next_frame() local
61 reliable = false; in unwind_next_frame()
74 reliable = true; in unwind_next_frame()
84 reliable = true; in unwind_next_frame()
99 state->reliable = reliable; in unwind_next_frame()
115 bool reliable, reuse_sp; in __unwind_start() local
141 reliable = true; in __unwind_start()
146 reliable = false; in __unwind_start()
160 state->reliable = reliable; in __unwind_start()
|
| /Linux-v5.4/arch/openrisc/kernel/ |
| 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
|
| D | stacktrace.c | 25 save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
29 if (!reliable) in save_stack_address()
48 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
52 if (!reliable) in save_stack_address_nosched()
|
| /Linux-v5.4/arch/um/kernel/ |
| 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()
|
| D | sysrq.c | 18 static void _print_addr(void *data, unsigned long address, int reliable) in _print_addr() argument
20 pr_info(" [<%08lx>] %s%pS\n", address, reliable ? "" : "? ", in _print_addr()
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| 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 delievered
|
| /Linux-v5.4/arch/sh/kernel/ |
| D | stacktrace.c | 26 static void save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
30 if (!reliable) in save_stack_address()
56 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
60 if (!reliable) in save_stack_address_nosched()
|
| D | dumpstack.c | 46 void printk_address(unsigned long address, int reliable) in printk_address() argument
49 reliable ? "" : "? ", (void *) address); in printk_address()
118 static void print_trace_address(void *data, unsigned long addr, int reliable) in print_trace_address() argument
121 printk_address(addr, reliable); in print_trace_address()
|
| D | perf_callchain.c | 19 static void callchain_address(void *data, unsigned long addr, int reliable) in callchain_address() argument
23 if (reliable) in callchain_address()
|
| /Linux-v5.4/net/rds/ |
| D | Kconfig | 4 tristate "The Reliable Datagram Sockets Protocol"
7 The RDS (Reliable Datagram Sockets) protocol provides reliable,
|
| /Linux-v5.4/arch/x86/kernel/ |
| D | tsc_msr.c | 125 * TSC is reliable. We were told by silicon design team that TSC in cpu_khz_from_msr()
126 * on Atom SoCs are always "reliable". TSC is also the only in cpu_khz_from_msr()
127 * reliable clocksource on these SoCs (HPET is either not present in cpu_khz_from_msr()
128 * or not functional) so mark TSC reliable which removes the in cpu_khz_from_msr()
|
| D | dumpstack.c | 67 static void printk_stack_address(unsigned long address, int reliable, in printk_stack_address() argument
71 printk("%s %s%pB\n", log_lvl, reliable ? "" : "? ", (void *)address); in printk_stack_address()
227 int reliable = 0; in show_trace_log_lvl() local
243 reliable = 1; in show_trace_log_lvl()
258 printk_stack_address(real_addr, reliable, log_lvl); in show_trace_log_lvl()
260 if (!reliable) in show_trace_log_lvl()
|
| /Linux-v5.4/drivers/net/wan/ |
| 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"
142 int reliable; member
523 if (state(hdlc)->reliable && !pvc->state.exist) { in fr_lmi_send()
565 static void fr_set_link_state(int reliable, struct net_device *dev) in fr_set_link_state() argument
570 state(hdlc)->reliable = reliable; in fr_set_link_state()
571 if (reliable) { in fr_set_link_state()
603 int i, cnt = 0, reliable; in fr_timer() local
607 reliable = state(hdlc)->request && in fr_timer()
[all …]
|
| /Linux-v5.4/drivers/acpi/ |
| D | button.c | 176 * On most platforms, the lid device is reliable. However in acpi_lid_notify_state()
187 * reliable. in acpi_lid_notify_state()
188 * 2. The open event may not be reliable. in acpi_lid_notify_state()
189 * 3. The close event is reliable. in acpi_lid_notify_state()
194 * platform triggered reliable event. By inserting a in acpi_lid_notify_state()
196 * platform triggered reliable one can always be seen by in acpi_lid_notify_state()
203 * as "close" is reliable and wrong "open" won't in acpi_lid_notify_state()
206 * "open" as "open" is not reliable and wrong in acpi_lid_notify_state()
216 /* Send the platform triggered reliable event */ in acpi_lid_notify_state()
|
| /Linux-v5.4/drivers/mtd/devices/ |
| D | docg3.c | 54 "2=reliable) : MLC normal operations are in normal mode");
303 * doc_set_data_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 …]
|
| 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-v5.4/drivers/bluetooth/ |
| 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-v5.4/include/linux/ |
| D | stacktrace.h | 32 * @reliable: True when the stack entry is reliable. Required by
39 bool reliable);
|
| /Linux-v5.4/kernel/ |
| D | stacktrace.c | 82 bool reliable) in stack_trace_consume_entry() argument
98 bool reliable) in stack_trace_consume_entry_nosched() argument
102 return stack_trace_consume_entry(cookie, addr, reliable); in stack_trace_consume_entry_nosched()
188 * reliable and returns the number of entries stored.
341 * reliable and returns the number of entries stored.
|
| /Linux-v5.4/Documentation/networking/ |
| D | x25-iface.txt | 73 The X.25 packet layer protocol depends on a reliable datalink service.
74 The LAPB protocol provides such reliable service. But this reliability
89 Thus, driver authors should make netif_rx() as reliable as possible:
|
| D | tcp-thin.txt | 3 A wide range of Internet-based services that use reliable transport
46 reliable transport"
|
| D | rds.txt | 14 RDS provides reliable, ordered datagram delivery by using a single
15 reliable connection between any two nodes in the cluster. This allows
34 reliable IB connection; the IP address is used exclusively to
93 transparently establish the underlying reliable connection
212 One might think that with reliable IB connections you wouldn't need
|
| /Linux-v5.4/drivers/media/rc/img-ir/ |
| 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-v5.4/tools/objtool/Documentation/ |
| D | stack-validation.txt | 12 that stack traces can be reliable.
33 a) More reliable stack traces for frame pointer enabled kernels
51 For stack traces based on frame pointers to be reliable, all
102 reliable even when interrupts or exceptions are involved.
110 stack traces need to be reliable (or an unreliable condition needs to
|
| /Linux-v5.4/drivers/gpu/drm/amd/display/dc/dce/ |
| D | dce_aux.h | 72 * But the SW timeout of 600usec is not reliable,
76 * 700usec is the minimum reliable SW timeout for polling
|
