From: Joerg Roedel <joerg.roedel@amd.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: pci_get_dev_by_id() from interrupt handlers
Date: Tue, 20 Apr 2010 18:04:24 +0200 [thread overview]
Message-ID: <20100420160423.GD31537@amd.com> (raw)
Hi Jesse,
I have a question regarding the warning in the pci_get_dev_by_id()
[search.c] function which triggers when called from interrupt context.
As far as I have seen this function should be save to be called in
atomic mode. Is there any other reason it should not be called in
interrupt handlers? I need to (indirectly) call this function for my
IOMMU driver to handle events from the IOMMU.
Thanks,
Joerg
next reply other threads:[~2010-04-20 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 16:04 Joerg Roedel [this message]
2010-04-20 16:32 ` pci_get_dev_by_id() from interrupt handlers Greg KH
2010-04-20 17:35 ` Joerg Roedel
2010-04-20 17:52 ` Greg KH
2010-04-21 10:05 ` Joerg Roedel
2010-04-21 10:21 ` Peter Zijlstra
2010-04-21 10:41 ` Joerg Roedel
2010-04-21 10:46 ` Peter Zijlstra
2010-04-21 10:55 ` Joerg Roedel
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=20100420160423.GD31537@amd.com \
--to=joerg.roedel@amd.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox