From: "Pali Rohár" <pali@kernel.org>
To: linux-pci@vger.kernel.org
Subject: PCI service interrupt handlers & access to PCI config space
Date: Sat, 10 Apr 2021 14:28:45 +0200 [thread overview]
Message-ID: <20210410122845.nhenihbygmcjlegn@pali> (raw)
Hello!
I see that more PCI service drivers in their interrupt handlers are
accessing PCI config space.
E.g. in PCIe Hot Plug interrupt handler pciehp_isr handler is called
pcie_capability_read_word() function.
It is correct? Because these capability functions are protected by
pci_lock_config() / pci_unlock_config() calls.
And what would happen when during execution of reading or writing to
PCIe config space (e.g. via pcie_capability_read_word()) is triggered
PCIe HP interrupt? Would not enter interrupt handler function in
deadlock (waiting for unlocking config space)?
next reply other threads:[~2021-04-10 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 12:28 Pali Rohár [this message]
2021-04-10 14:25 ` PCI service interrupt handlers & access to PCI config space Lukas Wunner
2021-04-10 15:17 ` Pali Rohár
2021-04-10 16:26 ` Lukas Wunner
2021-04-12 2:25 ` Keith Busch
2021-04-12 14:04 ` Pali Rohár
2021-04-12 15:09 ` Keith Busch
2021-04-13 9:33 ` Pali Rohár
2021-04-13 9:35 ` Pali Rohár
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=20210410122845.nhenihbygmcjlegn@pali \
--to=pali@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