Re: Handling PCI interrupts

DLL) that there is data to processed. Perhaps my understanding is not
accurate, but it seems to me that drivers can only respond to I/O requests
from above in the I/O stack, or they can generate I/O requests to pass down
the stack. A driver cannot create a new I/O request and pass it up the stack
(towards user-space), correct?

Correct.

3) could I create an I/O request, perhaps with an IOCTL, and somehow keep it
around in the driver until an interrupt occurs, and then complete the I/O
request? Is this the normal way for handling such a situation?

Exactly so, this is the normal way.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

.

Relevant Pages

  • Re: [PATCH 0/3] New firewire stack
    ... My main point about ohci1394 (the old stacks PCI driver) is, ... The big problems in the ohci1394 drivers is the irq_handler, bus reset ... reset, so there is no need to complicate the core stack with this extra state, ... interfaces have slightly disjoint feature sets and can't really be phased out. ...
    (Linux-Kernel)
  • Re: [PATCH 0/3] New firewire stack
    ... My main point about ohci1394 (the old stacks PCI driver) is, ... The big problems in the ohci1394 drivers is the irq_handler, bus reset ... reset, so there is no need to complicate the core stack with this extra state, ... interfaces have slightly disjoint feature sets and can't really be phased out. ...
    (Linux-Kernel)
  • [crash] BUG: unable to handle kernel NULL pointer dereference at (null), last sysfs file: /sys/devic
    ... Stack: ... Call Trace: ... # SCSI device support ... # You can enable one or both FireWire driver stacks. ...
    (Linux-Kernel)
  • Re: Driver getting Page Fault 0Eh Fault=0000, only when 2 PCI cards present in system
    ... There certainly are stack limits that a poorly designed function can exceed, ... > Is there a size issue on the size of a subroutine in a driver? ... With only one of our PCI cards ... >> area in Memory Space and also uses 1 PCI interrupt. ...
    (microsoft.public.development.device.drivers)
  • Re: how to test RAM?
    ... Driver Verifier. ... REPEAT THE LAST TABLE O N L Y) or match the fault address to the driver. ... Memory corruption, other hardware ... A kernel stack overflow. ...
    (microsoft.public.windowsxp.general)