From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
eger@cc.gatech.edu
Subject: Re: PCI Power Management / Interrupt Context
Date: Wed, 27 Jun 2001 14:49:16 -0400 [thread overview]
Message-ID: <3B3A2AAC.A4852671@mandrakesoft.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0106262208240.3824-100000@oscar.cc.gatech.edu> <200106271841.f5RIfR432746@penguin.transmeta.com>
Linus Torvalds wrote:
>
> In article <Pine.SOL.4.21.0106262208240.3824-100000@oscar.cc.gatech.edu>,
> David T Eger <eger@cc.gatech.edu> wrote:
> >
> >So I'm writing some code for a PCI card that is a framebuffer device, and
> >happily filling in the functions for the probe() and remove() functions
> >when I read documentation (Documentation/pci.txt) which mentions that
> >remove() can be called from interrupt context.
>
> This used to be true for a short while for hot-plug CardBus. I don't
> think it is true any more - and if it is, that would be a bug.
>
> So I think it's the documentation that is in error, and we should just
> fix that.
>
> Jeff?
Correct, pci_driver::remove does not get called from interrupt context.
I don't know where the heck this thread is coming from ;-) The docs
appear to be correct:
> remove Pointer to a function which gets called whenever a device
> being handled by this driver is removed (either during
> deregistration of the driver or when it's manually pulled
> out of a hot-pluggable slot). This function always gets
> called from process context, so it can sleep.
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
prev parent reply other threads:[~2001-06-27 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 2:42 PCI Power Management / Interrupt Context David T Eger
2001-06-27 4:00 ` Jeff Garzik
2001-06-27 11:22 ` Alan Cox
2001-06-27 11:20 ` Alan Cox
2001-06-27 18:41 ` Linus Torvalds
[not found] ` <200106271841.f5RIfR432746@penguin.transmeta.com>
2001-06-27 18:49 ` Jeff Garzik [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=3B3A2AAC.A4852671@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=eger@cc.gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.