diff options
author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2012-04-24 13:15:18 -0600 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2012-04-30 16:47:26 -0600 |
commit | 977f857ca566a1e68045fcbb7cfc9c4acb077cf0 (patch) | |
tree | eca7bfd254d2beca6da23cf28e03a50c3d214707 /Documentation/static-keys.txt | |
parent | 66f75a5d028beaf67c931435fdc3e7823125730c (diff) | |
download | talos-op-linux-977f857ca566a1e68045fcbb7cfc9c4acb077cf0.tar.gz talos-op-linux-977f857ca566a1e68045fcbb7cfc9c4acb077cf0.zip |
PCI: move mutex locking out of pci_dev_reset function
The intent of git commit 6fbf9e7a90862988c278462d85ce9684605a52b2
"PCI: Introduce __pci_reset_function_locked to be used when holding
device_lock." was to have a non-locking function that would call
pci_dev_reset function.
But it fell short of that by just probing and not actually reseting
the device. To make that work we need a way to move the lock
around device_lock to not be in pci_dev_reset (as the caller of
__pci_reset_function_locked already holds said lock). We do this by
renaming pci_dev_reset to __pci_dev_reset and bubbling said mutex out
of __pci_dev_reset to pci_dev_reset (a wrapper around __pci_dev_reset).
The __pci_reset_function_locked can now call __pci_dev_reset without
having to worry about the dead-lock.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'Documentation/static-keys.txt')
0 files changed, 0 insertions, 0 deletions