Messages in this thread | | | Date | Tue, 13 Mar 2001 02:43:11 +0100 | Subject | Re: hotplug and interrupt context | From | Andreas Bombe <> |
| |
On Sun, Mar 11, 2001 at 10:18:18PM -0500, Jeff Garzik wrote: > Andreas Bombe wrote: > > > > I couldn't trace that down to be 100% sure and it's better to conform to > > design than implementation, so I'll ask: > > > > Do the probe and remove functions of a pci_driver have to be able to > > work in interrupt context? (i.e. GFP_ATOMIC and stuff) > > No, no interrupt context to worry about. It would really suck if you > couldn't sleep in pci_driver::probe :)
Very good. I wasn't sure since I saw GFP_ATOMIC allocations somewhere in the cardbus code which looked like it was in card initialization. But it's also confusing and somewhere was a note saying that some of this is obsolete code which is replaced elsewhere...
> For CardBus, it calls schedule_task ..
Another thing learned, thanks.
-- Andreas E. Bombe <andreas.bombe@munich.netsurf.de> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |