From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: alistair@popple.id.au, david@gibson.dropbear.id.au,
ruscur@russell.cc, mpe@ellerman.id.au,
Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v2 2/3] powerpc/eeh: Restore config from edev in eeh_pe_reset_and_recover()
Date: Fri, 22 Apr 2016 23:28:03 +1000 [thread overview]
Message-ID: <1461331687-1069-2-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
In-Reply-To: <1461331687-1069-1-git-send-email-gwshan@linux.vnet.ibm.com>
The function eeh_pe_reset_and_recover() is used to recover EEH
error when the passthrou device are transferred to guest and
backwards. The content in the device's config space will be lost
on PE reset issued in the middle of the recovery. The function
saves/restores it before/after the reset. However, config access
to some adapters like Broadcom BCM5719 at this point will causes
fenced PHB. The config space is always blocked and we save 0xFF's
that are restored at late point. The memory BARs are totally
corrupted, causing another EEH error upon access to one of the
memory BARs.
This restores the config space from the content saved to the
EEH device when it's populated, to resolve above issue.
Fixes: 5cfb20b9 ("powerpc/eeh: Emulate EEH recovery for VFIO devices")
Cc: stable@vger.kernel.org #v3.18+
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Reviewed-by: Russell Currey <ruscur@russell.cc>
---
arch/powerpc/kernel/eeh_driver.c | 39 ++-------------------------------------
1 file changed, 2 insertions(+), 37 deletions(-)
diff --git a/arch/powerpc/kernel/eeh_driver.c b/arch/powerpc/kernel/eeh_driver.c
index 1c7d703..ec6e889 100644
--- a/arch/powerpc/kernel/eeh_driver.c
+++ b/arch/powerpc/kernel/eeh_driver.c
@@ -163,22 +163,6 @@ static bool eeh_dev_removed(struct eeh_dev *edev)
return false;
}
-static void *eeh_dev_save_state(void *data, void *userdata)
-{
- struct eeh_dev *edev = data;
- struct pci_dev *pdev;
-
- if (!edev)
- return NULL;
-
- pdev = eeh_dev_to_pci_dev(edev);
- if (!pdev)
- return NULL;
-
- pci_save_state(pdev);
- return NULL;
-}
-
/**
* eeh_report_error - Report pci error to each device driver
* @data: eeh device
@@ -304,22 +288,6 @@ static void *eeh_report_reset(void *data, void *userdata)
return NULL;
}
-static void *eeh_dev_restore_state(void *data, void *userdata)
-{
- struct eeh_dev *edev = data;
- struct pci_dev *pdev;
-
- if (!edev)
- return NULL;
-
- pdev = eeh_dev_to_pci_dev(edev);
- if (!pdev)
- return NULL;
-
- pci_restore_state(pdev);
- return NULL;
-}
-
/**
* eeh_report_resume - Tell device to resume normal operations
* @data: eeh device
@@ -561,9 +529,6 @@ int eeh_pe_reset_and_recover(struct eeh_pe *pe)
/* Put the PE into recovery mode */
eeh_pe_state_mark(pe, EEH_PE_RECOVERING);
- /* Save states */
- eeh_pe_dev_traverse(pe, eeh_dev_save_state, NULL);
-
/* Issue reset */
ret = eeh_reset_pe(pe);
if (ret) {
@@ -578,8 +543,8 @@ int eeh_pe_reset_and_recover(struct eeh_pe *pe)
return ret;
}
- /* Restore device state */
- eeh_pe_dev_traverse(pe, eeh_dev_restore_state, NULL);
+ /* Restore device's config space */
+ eeh_pe_restore_bars(pe);
/* Clear recovery mode */
eeh_pe_state_clear(pe, EEH_PE_RECOVERING);
--
2.1.0
next prev parent reply other threads:[~2016-04-22 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:28 [PATCH v2 1/3] powerpc/eeh: Ignore error handlers in eeh_pe_reset_and_recover() Gavin Shan
2016-04-22 13:28 ` Gavin Shan [this message]
2016-04-26 10:21 ` [PATCH v2 2/3] powerpc/eeh: Restore config from edev " Gavin Shan
2016-04-22 13:28 ` [PATCH v2 3/3] powerpc/eeh: Drop unnecessary label in eeh_pe_change_owner() Gavin Shan
2016-04-26 5:29 ` [PATCH v2 1/3] powerpc/eeh: Ignore error handlers in eeh_pe_reset_and_recover() David Gibson
2016-04-26 10:17 ` Gavin Shan
2016-04-27 1:16 ` Gavin Shan
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=1461331687-1069-2-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=alistair@popple.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=ruscur@russell.cc \
/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;
as well as URLs for NNTP newsgroup(s).