Searched full:pending (Results 1 – 25 of 163) sorted by relevance
1234567
| /Documentation/virt/kvm/devices/ |
| D | xics.rst | 47 * Pending interrupt priority, 8 bits
48 Zero is the highest priority, 255 means no interrupt is pending.
50 * Pending IPI (inter-processor interrupt) priority, 8 bits
51 Zero is the highest priority, 255 means no IPI is pending.
53 * Pending interrupt source number, 24 bits
54 Zero means no interrupt pending, 2 means an IPI is pending
88 * Pending flag, 1 bit
90 This bit is 1 if the source has a pending interrupt, otherwise 0.
|
| D | s390_flic.rst | 9 pending interrupts. FLIC performs operations on this list.
15 - inspect currently pending interrupts (KVM_FLIC_GET_ALL_IRQS)
16 - purge all pending floating interrupts (KVM_DEV_FLIC_CLEAR_IRQS)
17 - purge one pending floating I/O interrupt (KVM_DEV_FLIC_CLEAR_IO_IRQ)
27 the list of pending interrupts.
42 All interrupts remain pending, i.e. are not deleted from the list of
43 currently pending interrupts.
49 Simply deletes all elements from the list of currently pending floating
62 Disables async page faults for the guest and waits until already pending
|
| D | arm-vgic-v3.rst | 139 GICR_ISPENDR0 registers get/set the value of the latched pending state for
144 For edge triggered interrupts, once an interrupt becomes pending (whether
148 triggered interrupt may be pending either because the level input is held
151 interrupt is no longer pending unless the guest also wrote to ISPENDR, and
153 the pending status if the line level is still being held high. (These
240 save all LPI pending bits into guest RAM pending tables.
242 The first kB of the pending table is not altered by this operation.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 140 queue and pending set.
150 the pending set and cleared when it is removed from it.
165 Pending Set
168 The pending set is the second of the two fundamental collections in the
173 Note that a packet may both be pending and queued if it has been
175 re-submission, packets are not removed from the pending set.
185 the EC, the packet is added to the pending set. Next, the packet's data is
193 pending packets, i.e. a limit on how many packets may be waiting for an ACK
208 to the corresponding pending packet (via sequence ID) and completing it, as
209 well as initiating re-submission of all currently pending packets on
[all …]
|
| /Documentation/filesystems/ |
| D | incfs.rst | 61 waiting for a pending read.
65 waiting for a pending read.
78 reads_delayed_min and reads_delayed_pending if incfs first waits for a pending
81 time spent waiting for the pending read, and reads_delayed_min_us, which is
|
| /Documentation/networking/ |
| D | proc_net_tcp.rst | 51 0 no timer is pending
52 1 retransmit-timer is pending
53 2 another timer (e.g. delayed ack or keepalive) is pending
56 4 zero window probe timer is pending
|
| /Documentation/virt/acrn/ |
| D | io-request.rst | 74 FREE -> PENDING -> PROCESSING -> COMPLETE -> FREE -> ...
77 - PENDING: a valid I/O request is pending in this slot
87 a. The I/O handler of the hypervisor will fill an I/O request with PENDING
92 d. The worker looks for the PENDING I/O requests, assigns them to different
|
| /Documentation/driver-api/ |
| D | io_ordering.rst | 9 chipset to flush pending writes to the device before any reads are posted. A
50 pending writes before actually posting the read to the chipset, preventing
|
| /Documentation/networking/devlink/ |
| D | devlink-reload.rst | 38 pending activation. If no limitation specified this action may involve
39 firmware reset. If no new image pending this action will reload current
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 74 After the channels are specified, each thread is set as pending. All threads
83 emitted. A thread for that specific channel is created and is now pending, the
84 pending thread is started once run is to 1.
166 name, once requested, the channel is registered and a pending thread is added to the test list.
200 print the list of currently pending tests.
|
| D | client.rst | 27 - Issue pending requests and wait for callback notification
263 added, it must be placed on the DMA engine drivers pending queue.
275 it to the pending queue. For this, see step 5, dma_async_issue_pending.
284 5. Issue pending DMA requests and wait for callback notification
286 The transactions in the pending queue can be activated by calling the
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-incfs | 47 result of waiting for a pending read.
53 result of waiting for a pending read.
|
| D | sysfs-class-chromeos | 21 - "cancel": Cancel a pending reboot.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm2835-armctrl-ic.txt | 22 pending" register, or 1/2 respectively for interrupts in the "IRQ pending
|
| /Documentation/bpf/ |
| D | map_lru_hash_update.dot | 36 label="Flush local pending,
73 (1) Unreferenced pending, or
74 (2) Any pending node"]
|
| /Documentation/driver-api/media/ |
| D | v4l2-event.rst | 51 (pending) events of that particular type.
143 Check if there's a pending event
146 Checking if there's a pending event is via:
152 This function returns the number of pending events. Useful when implementing
|
| /Documentation/translations/zh_CN/core-api/ |
| D | genericirq.rst | 243 desc->status |= pending | masked;
251 desc->status &= ~pending;
253 } while (status & pending);
|
| /Documentation/locking/ |
| D | robust-futexes.rst | 18 that says "there's a waiter pending", and the sys_futex(FUTEX_WAIT)
23 value) that there were waiter(s) pending, and does the
55 (virtual memory area descriptor) concept to have a notion of 'pending
63 approach had been pending for years, but they are still not completely
|
| D | rt-mutex.rst | 75 BTW, there is still technically a "Pending Owner", it's just not called
76 that anymore. The pending owner happens to be the top_waiter of a lock
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-dsp-keystone.txt | 14 pending.
|
| /Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 209 b). during the reset, driver will store the pending cmds
210 which not returned by FW to driver's pending queue. Driver
211 will re-issue those pending cmds again to FW after the OCR
283 1. Add the fix of pending in FW after deleted the logic drives.
360 make sure the FW will finish the pending cmd for KDUMP case.
384 driver schedules for cmd completion if there are pending cmds
435 routine for max 3 minutes for all pending command completion. Now driver will
496 resumed if pending cmd count reduces to 16 or 5 seconds has elapsed
520 …(hw_crit_error=1). If hw_crit_error==1, now we do not accept any processing of pending cmds/accept…
551 i. Send stop adapter to FW & Dump pending FW cmds before declaring adapter dead.
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-get-event.rst | 58 - There is no event pending, and the device is in non-blocking mode.
|
| /Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 17 Pending a change to compact the extended attribute key used to store
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 85 Make breakpoint pending on future shared library load? (y or [n]) y
86 Breakpoint 1 (btrfs_init_sysfs) pending.
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gdb-kernel-debugging.rst | 81 Make breakpoint pending on future shared library load? (y or [n]) y
82 Breakpoint 1 (btrfs_init_sysfs) pending.
|
1234567