diff options
| author | Sebastian Ott <sebott@linux.vnet.ibm.com> | 2013-12-18 16:46:02 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2013-12-30 11:28:47 +0100 |
| commit | fcf2f402937a6696f6fa2a1aa882c5075e5fac34 (patch) | |
| tree | e1a0020a0f2efce7444fe7ec7a166f662b71fd8c /arch | |
| parent | 36d9f4d3b68c7035ead3850dc85f310a579ed0eb (diff) | |
| download | linux-exynos-fcf2f402937a6696f6fa2a1aa882c5075e5fac34.tar.gz linux-exynos-fcf2f402937a6696f6fa2a1aa882c5075e5fac34.tar.bz2 linux-exynos-fcf2f402937a6696f6fa2a1aa882c5075e5fac34.zip | |
s390/pci: obtain function handle in hotplug notifier
When using the CLP interface to enable or disable a pci device a
valid function handle needs to be delivered. So far our assumption
was that we always have an up-to-date version of the function handle
(since it doesn't change when the device is in use). This assumption
is incorrect if the pci device is enabled or disabled outside of our
control. When we are notified about such a change we already receive
the new function handle. Just use it.
Reviewed-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/s390/pci/pci_event.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/s390/pci/pci_event.c b/arch/s390/pci/pci_event.c index 800f064b0da7..069607209a30 100644 --- a/arch/s390/pci/pci_event.c +++ b/arch/s390/pci/pci_event.c @@ -75,6 +75,7 @@ void zpci_event_availability(void *data) if (!zdev || zdev->state == ZPCI_FN_STATE_CONFIGURED) break; zdev->state = ZPCI_FN_STATE_CONFIGURED; + zdev->fh = ccdf->fh; ret = zpci_enable_device(zdev); if (ret) break; @@ -101,6 +102,7 @@ void zpci_event_availability(void *data) if (pdev) pci_stop_and_remove_bus_device(pdev); + zdev->fh = ccdf->fh; zpci_disable_device(zdev); zdev->state = ZPCI_FN_STATE_STANDBY; break; |