| /linux-4.1.27/arch/um/kernel/ |
| D | stacktrace.c | 23 int reliable = 0; in dump_trace() local
35 reliable = 0; in dump_trace()
39 reliable = 1; in dump_trace()
41 ops->address(data, addr, reliable); in dump_trace()
47 static void save_addr(void *data, unsigned long address, int reliable) in save_addr() argument
51 if (!reliable) in save_addr()
|
| D | sysrq.c | 18 static void _print_addr(void *data, unsigned long address, int reliable) in _print_addr() argument
21 pr_cont(" %s", reliable ? "" : "? "); in _print_addr()
|
| /linux-4.1.27/arch/x86/kernel/ |
| D | stacktrace.c | 18 __save_stack_address(void *data, unsigned long addr, bool reliable, bool nosched) in __save_stack_address() argument
22 if (!reliable) in __save_stack_address()
35 static void save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
37 return __save_stack_address(data, addr, reliable, false); in save_stack_address()
41 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
43 return __save_stack_address(data, addr, reliable, true); in save_stack_address_nosched()
|
| D | dumpstack.c | 28 static void printk_stack_address(unsigned long address, int reliable, in printk_stack_address() argument
32 (char *)data, (void *)address, reliable ? "" : "? ", in printk_stack_address()
157 static void print_trace_address(void *data, unsigned long addr, int reliable) in print_trace_address() argument
160 printk_stack_address(addr, reliable, data); in print_trace_address()
|
| /linux-4.1.27/arch/sh/kernel/ |
| D | stacktrace.c | 28 static void save_stack_address(void *data, unsigned long addr, int reliable) in save_stack_address() argument
32 if (!reliable) in save_stack_address()
60 save_stack_address_nosched(void *data, unsigned long addr, int reliable) in save_stack_address_nosched() argument
64 if (!reliable) in save_stack_address_nosched()
|
| D | dumpstack.c | 47 void printk_address(unsigned long address, int reliable) in printk_address() argument
50 reliable ? "" : "? ", (void *) address); in printk_address()
116 static void print_trace_address(void *data, unsigned long addr, int reliable) in print_trace_address() argument
119 printk_address(addr, reliable); in print_trace_address()
|
| D | perf_callchain.c | 22 static void callchain_address(void *data, unsigned long addr, int reliable) in callchain_address() argument
26 if (reliable) in callchain_address()
|
| /linux-4.1.27/drivers/net/wan/ |
| D | hdlc_fr.c | 144 int reliable; member
525 if (state(hdlc)->reliable && !pvc->state.exist) { in fr_lmi_send()
567 static void fr_set_link_state(int reliable, struct net_device *dev) in fr_set_link_state() argument
572 state(hdlc)->reliable = reliable; in fr_set_link_state()
573 if (reliable) { in fr_set_link_state()
604 int i, cnt = 0, reliable; in fr_timer() local
608 reliable = state(hdlc)->request && in fr_timer()
615 if (state(hdlc)->reliable) in fr_timer()
624 reliable = (cnt < state(hdlc)->settings.n392); in fr_timer()
627 if (state(hdlc)->reliable != reliable) { in fr_timer()
[all …]
|
| D | Kconfig | 298 Various DSCC4 bugs forbid any reliable software reset of the ASIC.
|
| /linux-4.1.27/drivers/mtd/devices/ |
| D | docg3.c | 313 doc_dbg("doc_set_reliable_mode(%s)\n", strmode[docg3->reliable]); in doc_set_reliable_mode()
314 switch (docg3->reliable) { in doc_set_reliable_mode()
825 int *ofs, int reliable) in calc_block_sector() argument
830 if (reliable == 1 || reliable == 2) in calc_block_sector()
838 if (reliable == 1 || reliable == 2) in calc_block_sector()
895 docg3->reliable); in doc_read_oob()
1036 docg3->reliable); in doc_block_isbad()
1069 calc_block_sector(from, &block0, &block1, &page, &ofs, docg3->reliable);
1211 &ofs, docg3->reliable); in doc_erase()
1218 docg3->reliable); in doc_erase()
[all …]
|
| D | docg3.h | 309 unsigned int reliable:2; member
|
| /linux-4.1.27/arch/sh/include/asm/ |
| D | kdebug.h | 14 extern void printk_address(unsigned long address, int reliable);
|
| D | stacktrace.h | 13 void (*address)(void *data, unsigned long address, int reliable);
|
| /linux-4.1.27/arch/um/include/asm/ |
| D | stacktrace.h | 13 void (*address)(void *data, unsigned long address, int reliable);
|
| /linux-4.1.27/arch/sh/oprofile/ |
| D | backtrace.c | 32 static void backtrace_address(void *data, unsigned long addr, int reliable) in backtrace_address() argument
|
| /linux-4.1.27/Documentation/networking/ |
| D | tcp-thin.txt | 3 A wide range of Internet-based services that use reliable transport
46 reliable transport"
|
| 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 | nf_conntrack-sysctl.txt | 38 This option is only relevant when "reliable connection tracking
42 Userspace can request "reliable event mode". When this mode is
|
| 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
36 reliable IB connection; the IP address is used exclusively to
94 transparently establish the underlying reliable connection
199 One might think that with reliable IB connections you wouldn't need
|
| D | sctp.txt | 7 reliable transport protocol, with congestion control, support for
|
| D | x25.txt | 28 the Internet using TCP/IP as a reliable link layer. RFC1613 specifies the
|
| D | ieee802154.txt | 21 - MAC - provides access to shared channel and reliable data delivery
|
| D | 00-INDEX | 182 - Background on the reliable, ordered datagram delivery method RDS.
|
| D | rxrpc.txt | 5 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP
38 reliable virtual connections using UDP over IPv4 (or IPv6) as the transport
|
| D | timestamping.txt | 97 acknowledged. This only makes sense for reliable protocols. It is
|
| D | arcnet.txt | 196 line. (In recent versions of the driver, autoprobing is much more reliable
|
| D | arcnet-hardware.txt | 44 but which makes transfers much more reliable than Ethernet does. In fact,
448 probably more reliable.
|
| /linux-4.1.27/drivers/media/rc/img-ir/ |
| D | Kconfig | 16 less reliable (due to lack of timestamps) and consumes more
25 signals in hardware. This is more reliable, consumes less processing
|
| /linux-4.1.27/net/rds/ |
| D | Kconfig | 6 The RDS (Reliable Datagram Sockets) protocol provides reliable,
|
| /linux-4.1.27/kernel/debug/kdb/ |
| D | kdb_cmds | 4 # registers) are not reliable this early. set and bp commands should
|
| /linux-4.1.27/arch/x86/oprofile/ |
| D | backtrace.c | 26 static void backtrace_address(void *data, unsigned long addr, int reliable) in backtrace_address() argument
|
| /linux-4.1.27/arch/x86/include/asm/ |
| D | stacktrace.h | 40 void (*address)(void *data, unsigned long address, int reliable);
|
| /linux-4.1.27/net/dcb/ |
| D | Kconfig | 12 requirements (highly reliable, no drops vs. best effort vs. low
|
| /linux-4.1.27/net/lapb/ |
| D | Kconfig | 9 the lower) part of the X.25 protocol. It offers a reliable
|
| /linux-4.1.27/fs/ceph/ |
| D | Kconfig | 13 reliable access to petabytes of storage.
|
| /linux-4.1.27/net/decnet/ |
| D | Kconfig | 8 Digital (now Compaq). It provides reliable stream and sequenced
|
| /linux-4.1.27/scripts/coccinelle/free/ |
| D | devm_free.cocci | 14 /// less reliable in these cases.
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | ads7828 | 56 There is no reliable way to identify this chip, so the driver will not scan
|
| D | w83627hf | 45 This driver supports ISA accesses, which should be more reliable
|
| D | asc7621 | 33 are active, they are not necessarily reliable or useful externally. We
|
| D | it87 | 105 longer supports this interface though, as it is slower and less reliable
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-platform-kim | 18 The maximum reliable baud-rate the host can support.
|
| D | dev-kmsg | 76 readable context of the message, for reliable processing in
|
| /linux-4.1.27/Documentation/ |
| D | irqflags-tracing.txt | 46 turn itself off. I.e. the lock validator will still be reliable. There
|
| D | pnp.txt | 198 define these functions if the driver already has a reliable method of detecting
|
| D | robust-futexes.txt | 60 reliable.
|
| D | svga.txt | 234 modes supplied by SVGA autodetection as they are more reliable.
|
| D | DMA-API.txt | 664 because it is not longer reliable.
|
| D | kernel-docs.txt | 122 Linux kernel, providing users with high performance and reliable,
|
| D | kernel-parameters.txt | 3707 [x86] reliable: mark tsc clocksource as reliable, this
|
| /linux-4.1.27/drivers/gpu/drm/nouveau/dispnv04/ |
| D | tvnv17.c | 159 bool reliable = get_tv_detect_quirks(dev, &tv_enc->pin_mask); in nv17_tv_detect() local
164 if (reliable) { in nv17_tv_detect()
197 if (!reliable) { in nv17_tv_detect()
|
| /linux-4.1.27/net/sctp/ |
| D | Kconfig | 18 "SCTP is a reliable transport protocol operating on top of a
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-pcf857x.txt | 9 of reset (if any). The only reliable solution for setting up line direction is
|
| /linux-4.1.27/Documentation/scsi/ |
| D | dc395x.txt | 100 reliable driver, there is a chance, that it will kill your valuable data.
|
| D | qlogicfas.txt | 46 if you have reliable hardware and connections it may be more useful to
|
| /linux-4.1.27/Documentation/pti/ |
| D | pti_intel_mid.txt | 21 a stable, reliable connection that will not break unless
|
| /linux-4.1.27/lib/ |
| D | Kconfig.kgdb | 13 CONFIG_FRAME_POINTER to aid in producing more reliable stack
|
| /linux-4.1.27/Documentation/x86/ |
| D | entry_64.txt | 82 use the faster check: the stack will be a reliable indicator of
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ubifs.txt | 87 if the flash media is highly reliable. The effect
|
| D | romfs.txt | 84 reliable, it does not require any tables, and it is very simple.
|
| D | ext2.txt | 287 scheme but less reliable. Both methods are equally resolvable by their
|
| D | spufs.txt | 43 contain reliable information.
|
| /linux-4.1.27/Documentation/connector/ |
| D | connector.txt | 139 Netlink itself is not a reliable protocol. That means that messages can
|
| /linux-4.1.27/Documentation/laptops/ |
| D | asus-laptop.txt | 173 Note: there is currently no reliable way to read display status on xxN
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | client.txt | 196 Not all DMA engine drivers can return reliable information for
|
| /linux-4.1.27/Documentation/fb/ |
| D | udlfb.txt | 154 roll over very quickly. To get reliable results, design
|
| /linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 99 "critical": Hardware not reliable.
308 is not reliable anymore.
|
| /linux-4.1.27/drivers/input/serio/ |
| D | Kconfig | 147 It is, however, incompatible with the old, reliable HIL keyboard
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | timestamping.txt | 62 The DMA time is measured using counters - typically the least reliable
|
| D | compress_offload.txt | 39 reliable audio-video synchronization, which requires precise
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.concap | 87 a connect_request will ask for establishing a reliable lapb
|
| /linux-4.1.27/Documentation/ide/ |
| D | ide.txt | 32 *** automatically detected by Linux. For safe, reliable operation with such
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | boot-options.txt | 129 Don't stop other CPUs on reboot. This can make reboot more reliable
|
| /linux-4.1.27/Documentation/input/ |
| D | event-codes.txt | 205 consecutive events is reliable on a reasonable time scale (hours).
|
| D | joystick-parport.txt | 46 source on any of their pins. So, if you want a reliable source of power
|
| /linux-4.1.27/Documentation/i2c/ |
| D | writing-clients | 213 devices. You need some reliable way to identify the supported devices
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 27 reliable and robust by protecting it from PCI errors, and giving
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 112 idle state, and possibly to prevent that to guarantee reliable device
|
| /linux-4.1.27/Documentation/vm/ |
| D | hugetlbpage.txt | 71 number of huge pages requested. This is the most reliable method of
|
| /linux-4.1.27/Documentation/power/ |
| D | swsusp.txt | 178 "shutdown" is most reliable (except on ACPI systems).
|
| D | pci.txt | 971 drivers implement it at least in the cases where there is a reliable way of
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 100 perfectly by the device tree in a consistent and reliable manner.
|
| /linux-4.1.27/arch/x86/kernel/cpu/ |
| D | perf_event.c | 2135 static void backtrace_address(void *data, unsigned long addr, int reliable) in backtrace_address() argument
|
| /linux-4.1.27/Documentation/mtd/ |
| D | nand_ecc.txt | 19 However NAND flash is not extremely reliable so some error detection
|
| /linux-4.1.27/arch/powerpc/ |
| D | Kconfig | 443 A robust mechanism to get reliable kernel crash dump with
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 558 callback can be used to implement reliable state sharing and
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 627 proved to be reliable.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | README | 519 very slow, and some servers may be reliable enough (to risk
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 659 reliable data transfer. The only way user programs can indicate what
|
| /linux-4.1.27/drivers/video/fbdev/ |
| D | Kconfig | 2466 reliable access under heavy main memory bus traffic situations.
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace.txt | 1873 - having a reliable call stack to draw function calls graph
|
| /linux-4.1.27/Documentation/s390/ |
| D | Debugging390.txt | 720 format for s/390 & z/Architecture as it is more reliable for debugging
|