Home
last modified time | relevance | path

Searched refs:lost (Results 1 – 149 of 149) sorted by relevance

/linux-4.4.14/Documentation/scsi/scsi_transport_srp/
Drport_state_diagram.dot2 node [shape = doublecircle]; running lost;
12 lost;
19 blocked -> lost [ label = "dev_loss_tmo\nexpired or\nsrp_stop_rport_timers()" ];
20 failfast -> lost [ label = "dev_loss_tmo\nexpired or\nsrp_stop_rport_timers()" ];
24 running -> lost [ label = "srp_stop_rport_timers()" ];
25 running_rta -> lost [ label = "srp_stop_rport_timers()" ];
/linux-4.4.14/samples/bpf/
Dtrace_output_user.c105 __u64 lost; in perf_event_read() member
106 } *lost = (void *) e; in perf_event_read() local
107 printf("lost %lld events\n", lost->lost); in perf_event_read()
/linux-4.4.14/Documentation/blockdev/drbd/
Dnode-states-8.dot9 Primary -> Unknown [ label = "connection lost" ]
10 Secondary -> Unknown [ label = "connection lost" ]
/linux-4.4.14/sound/core/
Dtimer_compat.c63 u32 lost; member
82 status.lost = tu->timeri->lost; in snd_timer_user_status_compat()
Dtimer.c1783 status.lost = tu->timeri->lost; in snd_timer_user_status()
1802 tu->timeri->lost = 0; in snd_timer_user_start()
1826 tu->timeri->lost = 0; in snd_timer_user_continue()
/linux-4.4.14/drivers/staging/lustre/lustre/include/
Dlustre_cfg.h204 char lost = s[last]; in lustre_cfg_string() local
207 if (lost != '\0') { in lustre_cfg_string()
209 index, s, lost); in lustre_cfg_string()
/linux-4.4.14/sound/firewire/
Damdtp-stream.c449 bool lost; in handle_in_packet() local
509 lost = false; in handle_in_packet()
511 lost = data_block_counter != s->data_block_counter; in handle_in_packet()
518 lost = data_block_counter != in handle_in_packet()
522 if (lost) { in handle_in_packet()
/linux-4.4.14/kernel/events/
Dring_buffer.c114 u64 lost; in perf_output_begin() member
134 have_lost = local_read(&rb->lost); in perf_output_begin()
187 lost_event.lost = local_xchg(&rb->lost, 0); in perf_output_begin()
198 local_inc(&rb->lost); in perf_output_begin()
Dinternal.h28 local_t lost; /* nr records lost */ member
Dcore.c6200 void perf_log_lost_samples(struct perf_event *event, u64 lost) in perf_log_lost_samples() argument
6208 u64 lost; in perf_log_lost_samples() member
6215 .lost = lost, in perf_log_lost_samples()
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt41 Check for lost events.
75 $ grep -i lost mydump.txt
76 which tells you exactly how many events were lost, or use
78 to view your kernel log and look for "mmiotrace has lost events" warning. If
79 events were lost, the trace is incomplete. You should enlarge the buffers and
Dftrace.txt475 overrun: The number of lost events due to overwriting when
489 dropped events: Events lost due to overwrite option being off.
590 lost due to the buffer filling up (250280 - 140080 = 110200 events
591 lost).
2246 Notice that we lost the sys_nanosleep.
/linux-4.4.14/arch/x86/kernel/cpu/
Dperf_event_intel_bts.c56 local_t lost; member
204 local_inc(&buf->lost); in bts_update()
405 !!local_xchg(&buf->lost, 0)); in intel_bts_interrupt()
432 !!local_xchg(&buf->lost, 0)); in bts_event_del()
Dintel_pt.h98 local_t lost; member
Dperf_event_intel_pt.c594 local_inc(&buf->lost); in pt_handle_status()
962 local_xchg(&buf->lost, 0)); in intel_pt_interrupt()
1057 local_xchg(&buf->lost, 0)); in pt_event_del()
/linux-4.4.14/tools/perf/util/
Dtool.h45 lost, member
Devent.h52 u64 lost; member
57 u64 lost; member
365 struct lost_event lost; member
Dsession.c313 if (tool->lost == NULL) in perf_tool__fill_defaults()
314 tool->lost = perf_event__process_lost; in perf_tool__fill_defaults()
1090 if (tool->lost == perf_event__process_lost) in machines__deliver_event()
1091 evlist->stats.total_lost += event->lost.lost; in machines__deliver_event()
1092 return tool->lost(tool, event, sample, machine); in machines__deliver_event()
1095 evlist->stats.total_lost_samples += event->lost_samples.lost; in machines__deliver_event()
1332 if (session->tool->lost == perf_event__process_lost && in perf_session__warn_about_errors()
Dpython.c209 member_def(lost_event, lost, T_ULONGLONG, "number of lost events"),
220 pevent->event.lost.id, pevent->event.lost.lost) < 0) { in pyrf_lost_event__repr()
Dmachine.c494 event->lost.id, event->lost.lost); in machine__process_lost_event()
502 sample->id, event->lost_samples.lost); in machine__process_lost_samples_event()
Ddata-convert-bt.c1120 .lost = perf_event__process_lost, in bt_convert__perf2ctf()
/linux-4.4.14/Documentation/arm/OMAP/
Domap_pm46 5. Return the number of times the device has lost context
103 device has lost its internal context. If context has been lost, the
/linux-4.4.14/drivers/atm/
Deni.h104 unsigned long lost; /* number of lost cells (RX) */ member
Deni.c1439 eni_dev->lost = 0; in start_tx()
1466 if (eni_boards) printk(KERN_INFO "loss: %ld\n",ENI_DEV(eni_boards)->lost);
1509 eni_dev->lost += eni_in(MID_STAT) & MID_OVFL_TRASH; in eni_int()
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dltc2941.txt18 lost when the battery is disconnected.
/linux-4.4.14/Documentation/virtual/kvm/
Dlocking.txt59 We dirty-log for gfn1, that means gfn2 is lost in dirty-bitmap.
77 Accessed bit and Dirty bit can not be lost.
111 The Dirty bit is lost in this case.
Dtimekeeping.txt494 solution to the problem has risen: the guest may need to become aware of lost
497 number of buggy variants of lost tick compensation are distributed across
/linux-4.4.14/include/sound/
Dtimer.h112 unsigned long lost; /* lost ticks */ member
/linux-4.4.14/arch/arm/nwfpe/
Dsoftfloat-macros135 number of bits given in `count'. Any bits shifted off are lost. The value
283 number of bits given in `count'. Any bits shifted off are lost. The value
302 by the number of bits given in `count'. Any bits shifted off are lost.
340 any carry out is lost. The result is broken into two 64-bit pieces which
360 modulo 2^192, so any carry out is lost. The result is broken into three
399 2^128, so any borrow out (carry out) is lost. The result is broken into two
418 Subtraction is modulo 2^192, so any borrow out (carry out) is lost. The
/linux-4.4.14/arch/arm/common/
Dvlock.S96 mov r0, #1 @ nonzero indicates that I lost
/linux-4.4.14/drivers/block/aoe/
Daoe.h129 ulong lost; member
Daoecmd.c822 if (ifp && ++ifp->lost > (t->nframes << 1) in rexmit_timer()
1205 ifp->lost = 0; in ktiocomplete()
/linux-4.4.14/drivers/staging/fwserial/
Dfwserial.h168 unsigned lost; member
Dfwserial.c600 port->stats.lost += n; in fwtty_rx()
1450 stats.tx_stall, stats.fifo_errs, stats.lost); in fwtty_debugfs_show_port()
/linux-4.4.14/arch/alpha/kernel/
Derr_marvel.c232 int lost = scratch & (1UL << 4); in marvel_print_po7_uncrr_sym() local
233 scratch &= ~lost; in marvel_print_po7_uncrr_sym()
240 if (lost) in marvel_print_po7_uncrr_sym()
/linux-4.4.14/Documentation/networking/
Dtcp-thin.txt21 In order to reduce application-layer latency when packets are lost,
Dcxacru.txt74 "lost"
Dphonet.txt182 intrinsic race condition whereby writability might be lost between the
Deql.txt232 I tried to fix up a PPP script/system for redialing lost PPP
Dcan.txt813 lost.
1060 re-started bus-errors arbit-lost error-warn error-pass bus-off
1107 "re-started bus-errors arbit-lost error-warn error-pass bus-off"
1108 Shows the number of restarts, bus and arbitration lost errors,
Dppp_generic.txt81 frame has been lost or dropped (for example, because of a FCS (frame
Dip-sysctl.txt137 have been lost. When ipfrag_max_dist is positive, an additional check
142 lost. The existing fragment queue will be dropped, and a new one
440 RACK: 0x1 enables the RACK loss detection for fast detection of lost
Dbonding.txt460 gratuitous ARP is lost, communication may be
2728 always available. This will likely result in lost packets, and a
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-transport-srp56 "dev_loss_tmo" timer has fired; "lost" after the
/linux-4.4.14/include/uapi/linux/
Di2o-dev.h114 int lost; member
Daudit.h419 __u32 lost; /* messages lost */ member
/linux-4.4.14/lib/
DKconfig.kmemcheck62 lost.
/linux-4.4.14/arch/metag/lib/
Ddivsi3.S95 BNZ $LIDMCLoop ! Was single bit in curbit lost?
/linux-4.4.14/tools/perf/
Dbuiltin-mem.c265 .lost = perf_event__process_lost, in cmd_mem()
Dbuiltin-inject.c677 .lost = perf_event__repipe, in cmd_inject()
Dbuiltin-report.c655 .lost = perf_event__process_lost, in cmd_report()
Dbuiltin-diff.c367 .lost = perf_event__process_lost,
Dbuiltin-kvm.c1337 kvm->tool.lost = process_lost_event; in kvm_events_live()
Dbuiltin-trace.c1618 "LOST %" PRIu64 " events!\n", event->lost.lost); in trace__process_event()
Dbuiltin-sched.c1787 .lost = perf_event__process_lost, in cmd_sched()
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-floppy.1996-200257 * fix a lost interrupt problem. It appears the busy
/linux-4.4.14/Documentation/device-mapper/
Dcache.txt130 cache. If power is lost you may lose some recent writes. The metadata
143 dirty flags this data is lost if there's a crash so a safe fallback
148 there's a crash this information will be lost, which means the cache
Dthin-provisioning.txt129 a volatile write cache. If power is lost you may lose some recent
/linux-4.4.14/Documentation/DocBook/
Dusb.xml.db107 API-usb-root-hub-lost-power
Dkernel-api.xml.db505 API-pci-lost-interrupt
/linux-4.4.14/Documentation/usb/
Dpersist.txt57 has happened; look for lines saying "root hub lost power or was reset".
74 reset or otherwise had lost power) then it applies a persistence check
Drio.txt28 replace it with a fresh one. In my case, what happened is I lost two 16kb
Dpower-management.txt277 frequently result in lost keystrokes. Tests with mice show that some
313 since the device has probably lost most or all of its state
511 wakeup may fail and get lost. Which outcome occurs depends on timing
578 goes through during system suspend, i.e. the power session is lost. Any
609 hub interface driver is unbound, control of its child ports is lost and all
659 power session is lost the device may have been removed, or need reset.
Dmass-storage.txt113 least some Windows users do), the data may be lost.
Dusbmon.txt257 The member "dropped" is the number of events lost since the last call
Dproc_usb_info.txt135 For reasons lost in the mists of time, the Port number is always
/linux-4.4.14/drivers/media/dvb-core/
Ddvb_demux.c496 int start = pos, lost; in find_next_packet() local
505 lost = pos - start; in find_next_packet()
506 if (lost) { in find_next_packet()
/linux-4.4.14/drivers/usb/core/
DKconfig26 unplugged, causing any mounted filesystems to be lost. The
/linux-4.4.14/Documentation/filesystems/
Dlogfs.txt145 not consume any extra space, so the compression gains are lost space
148 However, they are not lost space to the filesystem internals. By
Drelay.txt322 be lost, if the number of unconsumed sub-buffers equals the total
325 enough, data will be lost in either case; the only difference is
326 whether data is lost from the beginning or the end of a buffer.
Dtmpfs.txt6 everything stored therein is lost.
Dhpfs.txt170 (lost files, unbalanced directories). (I guess all filesystem may do it).
191 When you have two (or more) lost directories pointing each to other, chkdsk
Dporting405 ->permission() and generic_permission()have lost flags
407 generic_permission() has also lost the check_acl argument; ACL checking
Dgfs2-glocks.txt134 glock is created. The per-glock statistics are lost when
Dseq_file.txt53 how the mechanism works without getting lost in other details. (Those
Dxfs-self-describing-metadata.txt31 up, the more likely that the cause will be lost in the noise. Hence the primary
Dext2.txt362 filesystem changes they represent are also lost).
/linux-4.4.14/Documentation/ABI/testing/
Ddev-kmsg45 sequence numbers allow to calculate the amount of lost
/linux-4.4.14/Documentation/hwmon/
Dadm1021111 FSB and faster) lost them, until the Core-based generation which
/linux-4.4.14/arch/arm/mach-omap1/
Dams-delta-fiq-handler.S197 beq hksw @ yes - key lost, next source
/linux-4.4.14/arch/arm/plat-omap/
DKconfig123 lost during off-mode entry on HS/EMU devices. This feature
/linux-4.4.14/Documentation/power/
Dstates.txt48 operating state is lost (the CPU retains power), so the system easily starts up
Dsuspend-and-cpuhotplug.txt222 when the CPUs are brought back online, since they wouldn't have lost the
Druntime_pm.txt617 * Remote wake-up events might have been lost by the firmware.
642 suspend attempts to be permanently lost. If the usage count goes to zero
/linux-4.4.14/Documentation/
DDMA-ISA-LPC.txt149 are lost when the system suspends so if your driver relies on the DMA
DManagementStyle89 deleting it, you may have irrevocably lost the trust of that
214 guy who lost his whole 36GB porn-collection because of your incompetence
Dkmemcheck.txt135 new error reports will be lost.
147 will get lost in that way instead. Try setting this to 10 or so on
Dedac.txt744 possible that some errors could be lost. With rdimm's, they display the
Dparport-lowlevel.txt353 returned, the port is lost to another driver and the port must be
DHOWTO437 again, sometimes things get lost in the huge volume.
Dkernel-parameters.txt2315 [NFSv4] Attempt to recover locks that were lost due
2319 after the locks are lost.
2324 not to attempt recovery of lost locks.
2630 interrupts *may* be lost!
DCodingStyle540 everything is lost: use "indent".
Dmemory-barriers.txt2923 assumed that the effect of the storage of V to *A is lost. Similarly:
Ddevices.txt55 messages a day, so mail sent to other addresses may very well get lost
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt147 /* we lost out in a seqno race, lock and retry.. */
180 /* we lost out in a seqno race, lock and retry.. */
/linux-4.4.14/arch/m68k/ifpsp060/
Dilsp.doc112 routine must make sure that the value isn't lost while popping
/linux-4.4.14/Documentation/console/
Dconsole.txt136 with the framebuffer console that suddenly lost all of its drivers.
/linux-4.4.14/tools/perf/Documentation/
Dintel-pt.txt121 resulting in data lost because the buffer was full. See 'Buffer handling' below
464 becomes full and some trace data is lost.
468 If trace data is lost, the driver sets 'truncated' in the PERF_RECORD_AUX event
686 Error events are new. They show where the decoder lost the trace. Error events
Dperf-script.txt113 Do various checks like samples ordering and lost events.
/linux-4.4.14/drivers/net/ppp/
Dppp_generic.c2126 int lost = 0, len = 0; in ppp_mp_reconstruct() local
2150 lost = 1; in ppp_mp_reconstruct()
2174 lost = 0; in ppp_mp_reconstruct()
2181 if (lost == 0 && (PPP_MP_CB(p)->BEbits & E) && in ppp_mp_reconstruct()
/linux-4.4.14/Documentation/video4linux/bttv/
DInsmod-options61 messages are lost (16 is known to work on
/linux-4.4.14/Documentation/connector/
Dconnector.txt140 be lost due to memory pressure or process' receiving queue overflowed,
/linux-4.4.14/fs/
DKconfig124 lost.
/linux-4.4.14/include/uapi/sound/
Dasound.h746 unsigned int lost; /* counter of master tick lost */ member
/linux-4.4.14/Documentation/fb/
Dviafb.txt224 If there are no output devices printed the output of this iga is lost.
/linux-4.4.14/
DREPORTING-BUGS29 lost in the noise of a mailing list that gets 1000+ emails a day.
DCREDITS2487 D: Minor kernel hacker for other lost causes (Hercules mono, etc).
DMAINTAINERS1115 M: Paul Parsons <lost.distance@yahoo.com>
/linux-4.4.14/drivers/net/wireless/mwifiex/
DREADME149 num_evt_link_lost = <number of link lost events received from device>
/linux-4.4.14/include/linux/
Dperf_event.h847 perf_log_lost_samples(struct perf_event *event, u64 lost);
/linux-4.4.14/fs/affs/
DChanges162 This was fixed before, but somehow got lost.
/linux-4.4.14/Documentation/scheduler/
Dcompletion.txt78 enqueued tasks could get "lost" - use reinit_completion() in that case.
/linux-4.4.14/net/ipv6/netfilter/
DKconfig319 if the interface goes down, those connections are lost. This is
/linux-4.4.14/tools/usb/usbip/
DINSTALL188 variables may be lost. In order to avoid this problem, you should set
/linux-4.4.14/Documentation/sound/alsa/
Dcompress_offload.txt202 are lost during transmission. This may be added in the future.
/linux-4.4.14/kernel/trace/
Dring_buffer.c4940 unsigned long lost; in test_ringbuffer() local
4967 while ((event = ring_buffer_consume(buffer, cpu, NULL, &lost))) { in test_ringbuffer()
4968 total_lost += lost; in test_ringbuffer()
DKconfig605 was written, the sizes, what was read, what was lost, and
/linux-4.4.14/net/ipv4/netfilter/
DKconfig290 if the interface goes down, those connections are lost. This is
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt8 application tried to write is most likely lost.
/linux-4.4.14/Documentation/isdn/
DINTERFACE747 parm.errcode= ISDN_STAT_L1ERR_SEND: Packet lost while sending.
748 ISDN_STAT_L1ERR_RECV: Packet lost while receiving.
/linux-4.4.14/drivers/tty/serial/8250/
DKconfig22 be lost when the driver is unloaded. This limitation may be lifted
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt282 - HCI: if an internal HCI error happens (frame is lost), or HCI is reported an
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt325 -- If a SCSI error occurs for the root device, all is lost unless
/linux-4.4.14/scripts/
Dspelling.txt595 losted||lost
/linux-4.4.14/Documentation/vm/
Dcleancache.txt250 of cleancache would be lost because the cache of pages in cleanache
Dfrontswap.txt43 in swap device writes is lost (and also a non-trivial performance advantage)
/linux-4.4.14/net/ipv4/
Dtcp_input.c2232 int lost = tp->fackets_out - tp->reordering; in tcp_update_scoreboard() local
2233 if (lost <= 0) in tcp_update_scoreboard()
2234 lost = 1; in tcp_update_scoreboard()
2235 tcp_mark_head_lost(sk, lost, 0); in tcp_update_scoreboard()
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Didle-states.txt279 lost on state entry, otherwise it is retained.
/linux-4.4.14/Documentation/development-process/
D5.Posting97 lost.
/linux-4.4.14/kernel/
Daudit.c850 s.lost = atomic_read(&audit_lost); in audit_receive_msg()
/linux-4.4.14/Documentation/scsi/
DChangeLog.1992-1997760 hog memory). Use other patches which got lost from 1.1.68.
1421 * aha1542.c (aha1542_abort): Look for lost interrupts, OGMB still
1680 Fix bug where sometimes portions of blocks would get lost
DChangeLog.megaraid_sas142 5. Fix bug where AENs could be lost in probe() and resume().
Dncr53c8xx.txt1023 to enable it, or at most enable this feature for the case the chip lost
DChangeLog.lpfc1149 * Fix crash when link is lost. This was due to lpfc_delay_iodone
/linux-4.4.14/Documentation/s390/
Dcds.txt368 can handle lost data on the network to allow for enhanced I/O processing.
/linux-4.4.14/drivers/char/
DKconfig262 save a few bits of very important data that may not be lost over
/linux-4.4.14/drivers/rtc/
DKconfig903 to lost interrupts, as reading Control Register C will clear
916 all pending IRQ flags - this can cause lost interrupts.
/linux-4.4.14/arch/arm/mm/
DKconfig936 rare circumstances, due to this erratum, write data can be lost when
/linux-4.4.14/drivers/platform/x86/
DKconfig439 be lost when one changes LED state.
/linux-4.4.14/scripts/dtc/
Ddtc-lexer.lex.c_shipped282 /* yy_hold_char holds the character lost when yytext is formed. */
/linux-4.4.14/scripts/genksyms/
Dlex.lex.c_shipped271 /* yy_hold_char holds the character lost when yytext is formed. */
/linux-4.4.14/scripts/kconfig/
Dzconf.lex.c_shipped299 /* yy_hold_char holds the character lost when zconftext is formed. */
/linux-4.4.14/Documentation/video4linux/
Dv4l2-framework.txt1067 This way no status information is lost, just the intermediate steps leading
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES718 allocation size miscalculation. After oplock token lost do not read through
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.seq1299 * lost by some other type of SCSI I/O (e.g. PIO). If we have
Daic79xx.seq1883 * have lost the race (e.g. host paused us) and our attempts
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt546 cleanly (0x2413) before power is lost. They must be acted upon, as the
/linux-4.4.14/arch/arm/
DKconfig1087 situation in which recent store transactions to the L2 cache are lost
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2338 hosts, where there's a bug which causes signals to UML to be lost,