Home
last modified time | relevance | path

Searched refs:issue (Results 1 – 200 of 212) sorted by relevance

12

/linux-4.4.14/Documentation/kbuild/
DKconfig.recursion-issue-011 # Simple Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
41 # implications of this recursive issue where the solution is perhaps not so
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
DKconfig.recursion-issue-021 # Cumulative Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
30 # other bells in the system cannot negate. The reason for this issue is
41 # For an example real world scenario issue refer to the attempt to remove
DKconfig.select-break1 # Select broken dependency issue
13 # example of this issue is below.
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
Dkconfig-language.txt401 into a recursive dependency issue with Kconfig, a recursive dependency can be
407 Kconfig recursive issue" subsection below. Kconfig does not do recursive
414 Simple Kconfig recursive issue
417 Read: Documentation/kbuild/Kconfig.recursion-issue-01
421 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
423 Cumulative Kconfig recursive issue
426 Read: Documentation/kbuild/Kconfig.recursion-issue-02
430 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
432 Practical solutions to kconfig recursive issue
435 Developers who run into the recursive Kconfig issue have three options
[all …]
/linux-4.4.14/net/irda/ircomm/
Dircomm_event.c99 ret = self->issue.connect_request(self, skb, info); in ircomm_state_idle()
158 ret = self->issue.connect_response(self, skb); in ircomm_state_waitr()
162 ret = self->issue.disconnect_request(self, skb, info); in ircomm_state_waitr()
190 ret = self->issue.data_request(self, skb, 0); in ircomm_state_conn()
200 ret = self->issue.data_request(self, skb, skb->len); in ircomm_state_conn()
209 ret = self->issue.disconnect_request(self, skb, info); in ircomm_state_conn()
Dircomm_lmp.c344 self->issue.data_request = ircomm_lmp_data_request; in ircomm_open_lsap()
345 self->issue.connect_request = ircomm_lmp_connect_request; in ircomm_open_lsap()
346 self->issue.connect_response = ircomm_lmp_connect_response; in ircomm_open_lsap()
347 self->issue.disconnect_request = ircomm_lmp_disconnect_request; in ircomm_open_lsap()
Dircomm_ttp.c100 self->issue.data_request = ircomm_ttp_data_request; in ircomm_open_tsap()
101 self->issue.connect_request = ircomm_ttp_connect_request; in ircomm_open_tsap()
102 self->issue.connect_response = ircomm_ttp_connect_response; in ircomm_open_tsap()
103 self->issue.disconnect_request = ircomm_ttp_disconnect_request; in ircomm_open_tsap()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-usb-lvstest9 Write to this node to issue "Get Device Descriptor"
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
Dsysfs-fs-f2fs32 Controls the issue rate of segment discard commands.
58 Controls the issue rate of small discard commands.
Dsysfs-class-cxl223 Writing 1 will issue a PERST to card which may cause the card
Dsysfs-devices-power24 + "enabled\n" to issue the events;
/linux-4.4.14/drivers/net/ethernet/xilinx/
Dxilinx_axienet_mdio.c168 goto issue; in axienet_mdio_setup()
177 goto issue; in axienet_mdio_setup()
193 issue: in axienet_mdio_setup()
/linux-4.4.14/Documentation/networking/
Di40evf.txt45 If an issue is identified with the released source code on the supported
47 to the issue to e1000-devel@lists.sf.net
Dixgbevf.txt50 If an issue is identified with the released source code on the supported
52 to the issue to e1000-devel@lists.sf.net
Digbvf.txt78 If an issue is identified with the released source code on the supported
80 to the issue to e1000-devel@lists.sf.net
Di40e.txt115 If an issue is identified with the released source code on the supported
117 to the issue to e1000-devel@lists.sourceforge.net and copy
Digb.txt127 If an issue is identified with the released source code on the supported
129 to the issue to e1000-devel@lists.sf.net
Dixgb.txt347 cable assembly may resolve the issue.
355 the issue.
360 this situation occurs, using a different cable assembly may resolve the issue.
383 the available memory is heavily fragmented. This issue may be seen with PCI-X
431 If an issue is identified with the released source code on the supported
433 to the issue to e1000-devel@lists.sf.net
De100.txt181 If an issue is identified with the released source code on the supported
183 issue to e1000-devel@lists.sourceforge.net.
Dixgbe.txt322 known issue with Microsoft Windows Server 2008 VM that results in a "yellow
347 If an issue is identified with the released source code on the supported
349 to the issue to e1000-devel@lists.sf.net
Dgeneric-hdlc.txt122 If you have a problem with N2, C101 or PLX200SYN card, you can issue the
De1000.txt273 issue addressed by this parameter has never been observed on Intel
459 If an issue is identified with the released source code on the supported
461 to the issue to e1000-devel@lists.sf.net
De1000e.txt310 If an issue is identified with the released source code on the supported
312 to the issue to e1000-devel@lists.sf.net
DPLIP.txt99 above calculation. It isn't an important issue, unless the wire is faulty,
Dtuntap.txt19 In order to use the driver a program has to open /dev/net/tun and issue a
D6pack.txt21 normal data, so a data stream can be interrupted at any time to issue an
Ddl2k.txt121 it is necessary to issue the following command:
Dpktgen.txt44 This cleanup issue is specifically the case for the driver ixgbe
Drxrpc.txt321 RXRPC_ABORT srt Abort code Abort code to issue/received
486 A client would issue an operation by:
681 (2) Avoid having RxRPC call request_key() at the point of issue of a call or
Dspider_net.txt120 When this local ram fills up, the spider chip will issue an interrupt
Dcxgb.txt256 To solve this issue, you can add the HWADDR=<mac_address> key to the
Drds.txt204 the message is DMAed and processed. This is only a potential issue
Dvortex.txt323 mode. Otherwise, the negotiation fails. This has been an issue
Dscaling.txt156 CPU. If NUMA locality is not an issue, this could also be all CPUs in
Dpacket_mmap.txt32 most of the time there is no need to issue a single system call. Concerning
/linux-4.4.14/drivers/staging/goldfish/
DREADME10 a cleanliness issue not a correctness one)
/linux-4.4.14/drivers/staging/speakup/
DTODO11 The first issue has to do with the way speakup communicates with serial
34 Another issue seems to only happen on SMP systems. It seems
Dspkguide.txt60 the default one, then you may issue the following command at the boot
362 If you issue the above ls command, you will get back something like
615 If you have not already done so, issue the following commands as root:
623 issue the following command as root:
720 directory, and issue the command:
/linux-4.4.14/arch/alpha/lib/
Dstrlen.S34 nop # helps dual issue last two insns
/linux-4.4.14/Documentation/timers/
Dtimer_stats.txt33 To activate a sample period issue:
36 To stop a sample period issue:
DNO_HZ.txt126 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
/linux-4.4.14/arch/blackfin/mach-common/
Darch_checks.c55 # error You are using a part with anomaly 05000448, this issue causes random memory read/write fail…
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dsnps,dwc-qos-ethernet.txt20 - snps,write-requests: Number of write requests that the AXI port can issue.
22 - snps,read-requests: Number of read requests that the AXI port can issue.
/linux-4.4.14/Documentation/arm/SA1100/
DPangolin7 To compile for Pangolin, you must issue the following commands:
DBrutus6 To compile for Brutus, you must issue the following commands:
/linux-4.4.14/net/rxrpc/
Drxkad.c830 time_t issue, now; in rxkad_decrypt_ticket() local
918 issue = le32_to_cpu(stamp); in rxkad_decrypt_ticket()
922 issue = be32_to_cpu(stamp); in rxkad_decrypt_ticket()
926 _debug("KIV ISSUE: %lx [%lx]", issue, now); in rxkad_decrypt_ticket()
929 if (issue > now) { in rxkad_decrypt_ticket()
935 if (issue < now - life) { in rxkad_decrypt_ticket()
941 *_expiry = issue + life; in rxkad_decrypt_ticket()
/linux-4.4.14/Documentation/powerpc/
Dqe_firmware.txt87 flexibility and save h/w traps If new features are activated or an issue is
134 | | RX INIT | command, the host must issue another special|
136 | | | following that re-issue the ATM RX INIT |
146 | | | must issue another command. |
157 | | command | INIT command, user must issue this command |
Dhvcs.txt263 in the Q & A section for more on this issue.
277 When hvcs is being used to serve consoles this behavior is not a huge issue
Deeh-pci-error-recovery.txt177 user-space scripts that might issue commands such as "ifdown eth0"
/linux-4.4.14/Documentation/DocBook/
Dtracepoint.xml.db14 API-trace-block-rq-issue
Dkernel-api.xml.db684 API-blkdev-issue-flush
685 API-blkdev-issue-discard
686 API-blkdev-issue-write-same
687 API-blkdev-issue-zeroout
Dlibata.xml.db98 API-ata-qc-issue
/linux-4.4.14/include/net/irda/
Dircomm_core.h59 call_t issue; member
Dirda_device.h109 struct dongle_reg *issue; /* Registration info */ member
/linux-4.4.14/
DREPORTING-BUGS26 Identifying which part of the Linux kernel might be causing your issue
31 Instead, try to figure out which kernel subsystem is causing the issue,
40 Once you know the subsystem that is causing the issue, you should send a
60 If you can't figure out which subsystem caused the issue, you should file
/linux-4.4.14/Documentation/usb/
Dehci.txt109 the EHCI controller can issue interrupts.
148 Bulk transfers are most often used where throughput is an issue. It's
167 onto one bus does not get you 60 MByte/sec. The issue appears to be
182 you issue a control or bulk request you can often expect to learn that
210 transfers are fully scheduled, so the main issue is likely to be how
DWUSB-Design-overview.txt317 exchange (FIXME: not yet done) and issue a /set address 0/ to bring the
372 we issue another URB to read into the destination buffer the chunk of
394 For IN xfers, we only issue URBs for the segments we want to read and
404 In dequeue() we are basically cancelling/aborting the transfer. We issue
Ddma.txt82 to fix this issue (for x86_32 machines with over 1 GByte of memory),
Dproc_usb_info.txt27 You can then issue `cat /proc/bus/usb/devices` to extract
69 would issue more ioctls to the device to communicate to it using
Dmass-storage.txt17 endpoints. With most device controllers this is not an issue, but
DURB.txt171 There is a lifetime issue to consider. An URB may complete at any
Dpower-management.txt125 allowed to issue dynamic suspends.
278 of them will issue a remote-wakeup request in response to button
/linux-4.4.14/Documentation/devicetree/bindings/iio/accel/
Dlis302.txt23 - st,click-single-{x,y,z}: if present, tells the device to issue an
26 - st,click-double-{x,y,z}: if present, tells the device to issue an
/linux-4.4.14/Documentation/
Dstable_kernel_rules.txt13 security issue, or some "oh, that's not good" issue. In short, something
16 be considered if they fix a notable performance or interactivity issue.
DCodeOfConflict19 will work to resolve the issue to the best of their ability. For more
Drtc.txt30 IRQ, so they can't all issue alarms; and where standard PC RTCs can
31 only issue an alarm up to 24 hours in the future, other hardware may
175 is connected to an IRQ line, it can often issue an alarm IRQ up to
178 * RTC_WKALM_SET, RTC_WKALM_RD ... RTCs that can issue alarms beyond
Dbtmrvl.txt96 Use hcitool to issue raw hci command, refer to hcitool manual
Dmd-cluster.txt161 3. Other nodes issue kobject_uevent_env with uuid and slot number
165 5. Other nodes issue either of the following depending on whether the disk
DSM501.txt42 The primary issue with memory allocation is that of moving the video
Dpwm.txt115 is an issue derived from the former barebone API and should be fixed soon.
Drfkill.txt112 rfkill devices issue uevents (with an action of "change"), with the following
Dcachetlb.txt249 Next, you have to solve the D-cache aliasing issue for all
276 If D-cache aliasing is not an issue, these two routines may
304 If D-cache aliasing is not an issue, this routine may
Dbcache.txt181 One last issue that sometimes trips people up is actually an old bug, due to
186 In practice this isn't an issue because as soon as a write comes along it'll
194 a fix for the issue there).
Dvolatile-considered-harmful.txt86 to be a "stupid legacy" issue (Linus's words) in this regard; fixing it
Ddebugging-via-ohci1394.txt83 This means that if you want to debug an issue in a system state where
Diostats.txt101 almost a non-issue. When the statistics are read, the per-CPU counters
Dstatic-keys.txt54 in the kernel this overhead may become more of an issue. In addition,
Drobust-futex-ABI.txt35 issue the system call:
Ddma-buf-sharing.txt406 Synchronization is an orthogonal issue to sharing the backing storage of a
439 multi-threaded app[3]. The issue is made worse when it is library code
Dstable_api_nonsense.txt133 security issue is found, it is fixed in a very short amount of time. A
Dunaligned-memory-access.txt159 capability, there is no issue with this code. But when the hardware isn't
Dworkqueue.txt115 (how many execution contexts are active) is an important issue. cmwq
DCodingStyle92 The other issue that always comes up in C styling is the placement of
769 help, and the maintenance issue of removing the inline when a second user
DSubmittingPatches187 If your patch fixes a bug in a specific commit, e.g. you found an issue using
593 A Fixes: tag indicates that the patch fixes an issue in a previous commit. It
Dxillybus.txt303 Note that the issue of partial buffer flushing is irrelevant for pipes having
Dmemory-barriers.txt199 the CPU will issue the following memory operations:
214 the CPU will only issue the following sequence of memory operations:
222 the CPU will only issue:
1646 to issue the loads in the correct order (eg. `a[b]` would have to load
Dpinctrl.txt1181 attempt to issue pinctrl_get_select_default() on these devices.
1282 The pins are allocated for your device when you issue the devm_pinctrl_get()
DDMA-API.txt178 wish to take advantage of it, you should issue a dma_set_mask()
DHOWTO133 developers, and help solve the issue.
Dkprobes.txt579 do_exit() case covered. do_execve() and do_fork() are not an issue.
/linux-4.4.14/drivers/scsi/arm/
Dacornscsi.h318 Queue_t issue; /* issue queue */ member
Dfas216.h284 Queue_t issue; /* issue queue */ member
Dfas216.c1926 SCpnt = queue_remove_exclude(&info->queues.issue, in fas216_kick()
2225 result = !queue_add_cmd_ordered(&info->queues.issue, SCpnt); in fas216_queue_command_lck()
2353 if (queue_remove_cmd(&info->queues.issue, SCpnt)) { in fas216_find_command()
2497 queue_remove_all_target(&info->queues.issue, target); in fas216_eh_device_reset()
2589 queue_remove_all_target(&info->queues.issue, SDpnt->id); in fas216_eh_bus_reset()
2860 if (!queue_initialise(&info->queues.issue)) in fas216_init()
2864 queue_free(&info->queues.issue); in fas216_init()
2952 queue_free(&info->queues.issue); in fas216_release()
Dacornscsi.c708 SCpnt = queue_remove_exclude(&host->queues.issue, host->busyluns); in acornscsi_kick()
2506 if (!queue_add_cmd_ordered(&host->queues.issue, SCpnt)) { in acornscsi_queuecmd_lck()
2558 if (queue_remove_cmd(&host->queues.issue, SCpnt)) { in acornscsi_do_abort()
2933 queue_initialise(&ashost->queues.issue); in acornscsi_probe()
2950 queue_free(&ashost->queues.issue); in acornscsi_probe()
2978 queue_free(&ashost->queues.issue); in acornscsi_remove()
/linux-4.4.14/Documentation/s390/
D3270.txt162 above? Use the grep command to find out; for instance, issue
168 issue "ls -l /dev/3270/tty620". The output should start with the
176 If so, you must issue the command "DEF GRAF 620" from your VM
258 Have a command you issue frequently? Assign it to a PF or PA key! Use
Dcds.txt144 applicable, the device drivers can use issue the READ DEVICE CHARACTERISTICS
153 only. See ccw_device_start() for more details. A device driver must never issue
157 ccw_device_halt() function. Some devices require to initially issue a HALT
182 must not issue ESA/390 I/O commands itself. Instead the ccw_device_start()
337 The device driver is allowed to issue the next ccw_device_start() call from
409 a long-running channel program or the device might require to initially issue
DDebugging390.txt803 To stop traces issue a
805 To delete a particular breakpoint issue
808 The PA1 key drops to CP mode so you can issue debugger commands,
888 If you want to issue a debugger command without halting your virtual machine
1081 On a SMP guest issue a command to all CPUs try prefixing the command with cpu
1082 all. To issue a command to a particular cpu try cpu <cpu number> e.g.
1086 from the bash prompt issue
1337 Format 1 (31 bit). These are typically used to issue read and write (and many
1350 issue a subsequent SENSE CCW command after the test subchannel.
1540 READY <devno> cause VM to issue a fake interrupt.
/linux-4.4.14/Documentation/gpio/
Ddrivers-on-gpio.txt42 userspace can issue the right system call to restart the system.
46 userspace can issue the right system call to power down the system.
Dgpio-legacy.txt60 is not the main issue; GPIOs are often used for the kind of board-specific
122 implementation issue, as are whether that support can leave "holes" in the space
140 misconfiguration is possible. You should normally issue these calls from
257 gpio_request() must be checked. You should normally issue these calls from
499 platform-specific issue, as are models like (not) having a one-to-one
542 gpio_chip and issue gpiochip_add(). Removing a GPIO controller should be
Ddriver.txt54 gpio_chip and issue gpiochip_add(). Removing a GPIO controller should be rare;
Dconsumer.txt154 is possible. You should normally issue these calls from a task context. However,
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt81 kernel_neon_end(), i.e., that it is only allowed to issue NEON/VFP instructions
91 * issue the calls to kernel_neon_begin(), kernel_neon_end() as well as the calls
DIXP4xx137 added. One issue with this board is that the mini-PCI slots only
/linux-4.4.14/Documentation/scsi/
DChangeLog.megaraid_sas211 will re-issue those pending cmds again to FW after the OCR
223 OCR to finish, then issue the cmds to FW.
247 context value larger than 32bit value issue.
252 3. driver fixed the device update issue after get the AEN
338 … Unexpected interrupt occurs in HWR Linux driver, add the dumy readl pci flush will fix this issue.
404 issue. 2. Increased MFI_POLL_TIMEOUT_SECS to 60 seconds from
DChangeLog.megaraid45 > does not help and issue still has been reproduced by simple
86 issue on 64-bit platform.
87 Customer reporeted "kernel unaligned access addrss" issue when
185 2. Fixed a issue: megaraid always fails to reset handler.
338 5. Fixed Tape drive issue : For any Direct CDB command to physical device
344 To address this issue, the 'timeout' field in the DCDB command will
Dmegaraid.txt23 Currently this module (called Common Management Module) is used only to issue
Dufs.txt88 * UIO_SAP: To issue commands to Unipro layers.
DChangeLog.lpfc15 * Fix for issue where not all luns are seen. Search all lists
87 * Fixed issue with receiving PLOGI handling when node is on NPR
253 * Fixed a use after free issue in lpfc_init.c.
306 * Fix issue where we are calling lpfc_disc_done() recursively from
737 * Added binary sysfs file to issue mbox commands
967 * Removed LPFC_DEV_RPTLUN node failure bit because we don't issue
1044 * On reset_lun, issue LUN_RESET as opposed to ABORT_TASK_SET.
1199 on PLOGI issue.
1818 * Removed several #ifdef powerpc, including for a discovery issue
Dscsi_mid_low_api.txt744 eh_bus_reset_handler - issue SCSI bus reset
745 eh_device_reset_handler - issue SCSI device reset
857 * eh_bus_reset_handler - issue SCSI bus reset
875 * eh_device_reset_handler - issue SCSI device reset
1293 level will issue a REQUEST_SENSE SCSI command to
1356 issue a REQUEST SENSE command.
Dscsi_eh.txt233 - EH reuses failed scmds to issue commands for recovery. For
Daic79xx.txt164 - Correct data corruption issue that occurred under
Dtmscsim.txt368 recover from a SCSI reset in time. Use a higher delay or don't issue
DChangeLog.sym53c8xx24 - Fix an issue in the ncr_int_udc() (unexpected disconnect)
/linux-4.4.14/Documentation/filesystems/
Dcramfs.txt26 issue.
Ddlmfs.txt25 DLM implementations should not be a major issue.
Dexofs.txt7 will in turn issue commands to the local OSD initiator.
Dautofs4-mount-control.txt12 directory that is being managed in order to be able to issue control
302 issue mount requests, the kernel communication pipe descriptor is released
Dxfs-self-describing-metadata.txt324 metadata. Once this is done, we can issue the IO.
Dext2.txt333 performance problems (although RAM size becomes an issue at this point).
Dpath-lookup.txt165 A related, but distinctly different, issue is that of rename atomicity versus
Dxfs-delayed-logging-design.txt83 be to able to issue enough transactions to keep the log buffers full and under
478 The big issue for a checkpoint transaction is the log space reservation for the
Dext4.txt344 discard Controls whether ext4 should issue discard/TRIM
/linux-4.4.14/arch/arm/boot/dts/
Dorion5x-lacie-ethernet-disk-mini-v2.dts88 * issue is sorted out in the MTD code, break this into at
Dorion5x-maxtor-shared-storage-2.dts67 * issue is sorted out in the MTD code, break this into at
Dorion5x-lacie-d2-network.dts107 * issue is sorted out in the MTD code, break this into at
Drk3288.dtsi183 * are not affected, this issue prevents 4GB from booting.
/linux-4.4.14/Documentation/power/
Dnotifiers.txt29 If all goes well, the restored kernel will issue a
Dbasic-pm-debugging.txt70 suspending devices) and issue the standard hibernation commands. For example,
133 work (of course, this only may be an issue on SMP systems) and the problem
Ddevices.txt169 whether or not a wakeup-capable device should issue wakeup events is a policy
642 PCI device may not perform DMA or issue IRQs, and any wakeup events it
703 to that document for more information regarding this particular issue as well as
Dfreezing-of-tasks.txt120 is a separate issue.]
/linux-4.4.14/Documentation/device-mapper/
Dcache-policies.txt11 The policy can return a simple HIT or MISS or issue a migration.
13 Currently there's no way for the policy to issue background work,
Dthin-provisioning.txt17 with depth. Fragmentation may still be an issue, however, in some
/linux-4.4.14/drivers/net/wireless/hostap/
Dhostap_hw.c326 int err, res, issue, issued = 0; in hfa384x_cmd() local
367 issue = list_empty(&local->cmd_queue); in hfa384x_cmd()
368 if (issue) in hfa384x_cmd()
375 if (!issue) in hfa384x_cmd()
502 int issue, ret; in hfa384x_cmd_callback() local
527 issue = list_empty(&local->cmd_queue); in hfa384x_cmd_callback()
528 if (issue) in hfa384x_cmd_callback()
534 if (issue && hfa384x_cmd_issue(dev, entry)) in hfa384x_cmd_callback()
/linux-4.4.14/Documentation/fb/
Ddeferred_io.txt35 whether to coalesce and issue SG DMA or to do memory bursts.
Dsstfb.txt43 plug the monitor to the "normal" video board in order to issue
/linux-4.4.14/Documentation/spi/
Dbutterfly20 issue interrupts to them. Later, your protocol driver should work
Dspi-summary377 As soon as it enters probe(), the driver may issue I/O requests to
544 spi_finalize_current_message() so the subsystem can issue the next
552 spi_finalize_current_transfer() so the subsystem can issue the next
/linux-4.4.14/drivers/dma/
Dzx296702_dma.c386 int issue = 0; in zx_dma_issue_pending() local
395 issue = 1; in zx_dma_issue_pending()
404 if (issue) in zx_dma_issue_pending()
/linux-4.4.14/Documentation/m68k/
DREADME.buddha98 The IDE ports issue an INT2. You can read the level of the
103 Catweasel expansion boards can issue an INT6. A separate
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt193 can function as a periodic timer, an additional once a day alarm, and can issue
510 potentially unsynchronized source. One issue which is not unique to the TSC,
521 serialization can pose a performance issue for hardware virtualization. An
594 compensate for slower I/O to and from devices. The first issue is not solvable
599 The second issue may cause performance problems, but this is unlikely to be a
600 significant issue. In many cases these delays may be eliminated through
Dlocking.txt113 In order to avoid this kind of issue, we always treat the spte as "volatile"
Dmmu.txt259 guest cr3. In this case, the guest is obliged to issue an invlpg instruction
373 it will simply be missed by the shadow page lookup code. A similar issue
Dapi.txt33 can be used to issue system ioctls. A KVM_CREATE_VM ioctl on this
34 handle will create a VM file descriptor which can be used to issue VM
1790 - if so, issue KVM_NMI
/linux-4.4.14/Documentation/input/
Djoystick-api.txt13 immediately after the open it will issue a series of synthetic events
50 As mentioned above, the driver will issue synthetic JS_EVENT_INIT ORed
/linux-4.4.14/Documentation/video4linux/
Dmeye.txt94 MEYEIOC_G_PARAMS, change what he likes and then issue the
Dpxa_camera.txt130 c) DMA hot chaining timeslice issue
/linux-4.4.14/Documentation/leds/
Dleds-class.txt82 would cause nightmare dependency issues. I see this as a minor issue
/linux-4.4.14/Documentation/mtd/nand/
Dpxa3xx-nand.txt36 So, in order to achieve reading (for instance), we issue several READ0 commands
/linux-4.4.14/drivers/md/
Ddm-cache-target.c885 static void issue(struct cache *cache, struct bio *bio) in issue() function
907 issue(cache, bio); in inc_and_issue()
1622 issue(cache, bio); in process_flush_bio()
1721 issue(cache, cell->holder); in remap_cell_to_origin_clear_discard()
1730 issue(cache, bio); in remap_cell_to_origin_clear_discard()
1755 issue(cache, cell->holder); in remap_cell_to_cache_dirty()
1766 issue(cache, bio); in remap_cell_to_cache_dirty()
Ddm-thin.c713 static void issue(struct thin_c *tc, struct bio *bio) in issue() function
745 issue(tc, bio); in remap_to_origin_and_issue()
752 issue(tc, bio); in remap_and_issue()
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt44 caller sleeps waiting for it. Thus, it is possible to issue multiple read commands to different
/linux-4.4.14/Documentation/x86/i386/
DIO-APIC.txt74 the PCI chipset. Most cards issue INTA, this creates optimal distribution
/linux-4.4.14/Documentation/w1/
Dw1.generic38 2. reading. This will issue reading eeprom response.
/linux-4.4.14/Documentation/block/
Dqueue-sysfs.txt36 large discards are issued, setting this value lower will make Linux issue
Dcfq-iosched.txt101 time for each process to issue I/O request before the cfq queue is switched.
Dbiodoc.txt280 the low level device capabilities or requires the ability to issue commands
612 [TBD: This is a potential issue, though a rare possibility
846 Andrew Morton's multi-page bio patches attempt to issue multi-page
/linux-4.4.14/Documentation/sound/alsa/
DAudiophile-Usb.txt128 issue with this mode, then you can skip the following chapter.
135 device. For instance, a particularly annoying issue is that the sound captured
258 * A workaround for this last issue has been applied to kernel 2.6.23, but it may not
Dtimestamping.txt128 will be required to issue multiple queries and perform an
/linux-4.4.14/Documentation/RCU/
Dchecklist.txt18 Another exception is where performance is not an issue, and RCU
345 is not an issue (or, more accurately, to the extent that it is
346 an issue, the memory-allocator locking handles it). However,
Drcu_dereference.txt61 This issue arises on some systems when a newly JITed function is
Dstallwarn.txt238 o A hardware or software issue shuts off the scheduler-clock
/linux-4.4.14/Documentation/vm/
Dslub.txt54 Trying to find an issue in the dentry cache? Try
251 After reporting the details of the issue encountered the FIX SLUB message
/linux-4.4.14/Documentation/filesystems/caching/
Doperations.txt52 Someone wanting to issue an operation should allocate something with this
/linux-4.4.14/arch/mips/
DKconfig.debug128 useful if you suspect there may be an issue with compact branches in
/linux-4.4.14/arch/arm/crypto/
Dsha1-armv4-large.S40 @ issue Cortex A8 core was measured to process input block in
45 @ Rescheduling for dual-issue pipeline resulted in 13% improvement on
Daes-armv4.S18 @ key [on single-issue Xscale PXA250 core].
26 @ Rescheduling for dual-issue pipeline resulted in 12% improvement on
Dsha512-core.S_shipped14 @ by gcc 3.4 and it spends ~72 clock cycles per byte [on single-issue
19 @ Rescheduling for dual-issue pipeline resulted in 6% improvement on
37 @ multiple NEON instructions per cycle, but dual NEON issue could
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt206 responsibility. This is usually non-issue because bus ops and
/linux-4.4.14/Documentation/power/regulator/
Dconsumer.txt193 - thermal management firmware that can issue an arbitrary I2C transaction to
/linux-4.4.14/Documentation/acpi/
Dmethod-tracing.txt83 interpretion, thus can aid issue debugging and performance tuning. Note
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt263 described before. This might be an issue in the following cases:
379 devices, it is recommended to issue a read towards internal registers using
392 to issue a software reset of the switch during this setup function in order to
/linux-4.4.14/Documentation/crypto/
Dasync-tx-api.txt91 Operations do not immediately issue after return from the
/linux-4.4.14/Documentation/blockdev/
Dzram.txt79 implemented as a special case by lock overhead issue and does not support
/linux-4.4.14/Documentation/cgroups/
Dunified-hierarchy.txt45 hierarchies can only be used in one. The issue is exacerbated by the
47 populated. Another issue is that all controllers bound to a hierarchy
185 One long-standing issue that cgroup faces is the competition between
/linux-4.4.14/arch/blackfin/
DKconfig.debug164 into a software buffer, for dumping when there is an issue. This
/linux-4.4.14/fs/reiserfs/
DREADME41 to address the fair crediting issue in the next GPL version.)
/linux-4.4.14/drivers/scsi/
Dips.c593 ha->func.issue = ips_issue_i2o_memio; in ips_setup_funclist()
613 ha->func.issue = ips_issue_i2o_memio; in ips_setup_funclist()
615 ha->func.issue = ips_issue_copperhead_memio; in ips_setup_funclist()
631 ha->func.issue = ips_issue_i2o; in ips_setup_funclist()
633 ha->func.issue = ips_issue_copperhead; in ips_setup_funclist()
3832 return ((*ha->func.issue) (ha, scb)); in ips_send_cmd()
Dips.h1010 int (*issue)(struct ips_ha *, struct ips_scb *); member
/linux-4.4.14/Documentation/dvb/
DREADME.dvb-usb104 - #if for 2.6.4 (dvb), compile issue
/linux-4.4.14/drivers/usb/misc/
DKconfig110 magazine published a modified version of this device in issue
/linux-4.4.14/Documentation/arm64/
Dbooting.txt232 kernel will issue CPU_ON calls as described in ARM document number ARM
/linux-4.4.14/Documentation/x86/
Dintel_mpx.txt203 Here, the solution for this issue is to hook do_munmap() to check
/linux-4.4.14/drivers/staging/rtl8723au/core/
Drtw_mlme_ext.c3969 int issue = 0; in send_beacon23a() local
3977 issue++; in send_beacon23a()
3986 } while (!bxmitok && issue<100 && !padapter->bSurpriseRemoved && in send_beacon23a()
3999 if (passing_time > 100 || issue > 3) in send_beacon23a()
4001 __func__, issue, poll, passing_time); in send_beacon23a()
/linux-4.4.14/drivers/staging/rtl8188eu/core/
Drtw_mlme_ext.c1965 int issue = 0; in send_beacon() local
1973 issue++; in send_beacon()
1979 } while (!bxmitok && issue < 100 && !padapter->bSurpriseRemoved && !padapter->bDriverStopped); in send_beacon()
1989 if (passing_time > 100 || issue > 3) in send_beacon()
1990 …DBG_88E("%s success, issue:%d, poll:%d, %u ms\n", __func__, issue, poll, rtw_get_passing_time_ms(s… in send_beacon()
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt239 will result in lock-class leakage. The issue here is that each
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt253 NFC_HCI_EVT_TARGET_DISCOVERED event from PN544 requires to issue an
/linux-4.4.14/Documentation/trace/
Dftrace-design.txt45 is a major issue at this point, especially in relation to the location of the
/linux-4.4.14/tools/perf/
Ddesign.txt321 * User-space reading this value should issue an rmb(), on SMP capable
/linux-4.4.14/scripts/
Dspelling.txt568 isssue||issue
/linux-4.4.14/Documentation/i2c/
Dwriting-clients128 problematic. Drivers for I2C devices that issue interrupts need more (and
/linux-4.4.14/drivers/acpi/
DKconfig464 issue.
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt74 The one last thing is that usually, slave devices won't issue DRQ by
/linux-4.4.14/Documentation/development-process/
D5.Posting154 another moment discussing this issue. When writing a changelog, you should
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt498 In addition to the EV_KEY events, thinkpad-acpi may also issue EV_SW
566 The driver will issue KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN events
1195 level to a safe setting if userspace does not issue one of the procfs
/linux-4.4.14/arch/s390/
DKconfig644 to issue asynchronous chsc commands (DANGEROUS).
/linux-4.4.14/Documentation/mtd/
Dnand_ecc.txt283 Anyway, if there is an issue: this code is developed on x86 (to be
/linux-4.4.14/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt163 interoperability with other networks will not be an issue. Implementations
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.seq1676 /* Post the SCBID in SINDEX and issue an interrupt */
2249 * The PCI module will only issue a PCI
Daic79xx.reg166 * request to issue a message.
1469 * The maximum number of commands to issue during a
Daic7xxx.reg912 * request to issue a message.

12