From: Andreas Bombe <andreas.bombe@munich.netsurf.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hotplug and interrupt context
Date: Tue, 13 Mar 2001 02:43:11 +0100 [thread overview]
Message-ID: <20010313024310.B2436@storm.local> (raw)
In-Reply-To: <20010312014811.B472@storm.local> <3AAC3FFA.1C3DDC0E@mandrakesoft.com>
In-Reply-To: <3AAC3FFA.1C3DDC0E@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, Mar 11, 2001 at 10:18:18PM -0500
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/
prev parent reply other threads:[~2001-03-13 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 0:48 hotplug and interrupt context Andreas Bombe
2001-03-12 3:18 ` Jeff Garzik
2001-03-13 1:43 ` Andreas Bombe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010313024310.B2436@storm.local \
--to=andreas.bombe@munich.netsurf.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.