From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Wei Yang <weiyang@linux.vnet.ibm.com>,
gwshan@linux.vnet.ibm.com, bhelgaas@google.com,
mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V10 08/12] powerpc/powernv: Support EEH reset for VF PE
Date: Fri, 30 Oct 2015 15:11:20 +1100 [thread overview]
Message-ID: <5632EDE8.2010601@ozlabs.ru> (raw)
In-Reply-To: <1445829362-2738-9-git-send-email-weiyang@linux.vnet.ibm.com>
On 10/26/2015 02:15 PM, Wei Yang wrote:
> PEs for VFs don't have primary bus. So they have to have their own reset
> backend, which is used during EEH recovery. The patch implements the reset
> backend for VF's PE by issuing FLR or AF FLR to the VFs, which are contained
> in the PE.
>
> [gwshan: changelog and code refactoring]
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> Acked-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> ---
> arch/powerpc/include/asm/eeh.h | 1 +
> arch/powerpc/platforms/powernv/eeh-powernv.c | 134 ++++++++++++++++++++++++++-
> 2 files changed, 134 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/include/asm/eeh.h b/arch/powerpc/include/asm/eeh.h
> index ec21f8f..331c856 100644
> --- a/arch/powerpc/include/asm/eeh.h
> +++ b/arch/powerpc/include/asm/eeh.h
> @@ -136,6 +136,7 @@ struct eeh_dev {
> int pcix_cap; /* Saved PCIx capability */
> int pcie_cap; /* Saved PCIe capability */
> int aer_cap; /* Saved AER capability */
> + int af_cap; /* Saved AF capability */
> struct eeh_pe *pe; /* Associated PE */
> struct list_head list; /* Form link list in the PE */
> struct pci_controller *phb; /* Associated PHB */
> diff --git a/arch/powerpc/platforms/powernv/eeh-powernv.c b/arch/powerpc/platforms/powernv/eeh-powernv.c
> index cfd55dd..017cd72 100644
> --- a/arch/powerpc/platforms/powernv/eeh-powernv.c
> +++ b/arch/powerpc/platforms/powernv/eeh-powernv.c
> @@ -404,6 +404,7 @@ static void *pnv_eeh_probe(struct pci_dn *pdn, void *data)
> edev->pcix_cap = pnv_eeh_find_cap(pdn, PCI_CAP_ID_PCIX);
> edev->pcie_cap = pnv_eeh_find_cap(pdn, PCI_CAP_ID_EXP);
> edev->aer_cap = pnv_eeh_find_ecap(pdn, PCI_EXT_CAP_ID_ERR);
> + edev->af_cap = pnv_eeh_find_cap(pdn, PCI_CAP_ID_AF);
> if ((edev->class_code >> 8) == PCI_CLASS_BRIDGE_PCI) {
> edev->mode |= EEH_DEV_BRIDGE;
> if (edev->pcie_cap) {
> @@ -893,6 +894,127 @@ static int pnv_eeh_bridge_reset(struct pci_dev *dev, int option)
> return 0;
> }
>
> +static void pnv_eeh_wait_for_pending(struct pci_dn *pdn, int pos,
> + u16 mask, bool af_flr_rst)
> +{
> + struct eeh_dev *edev = pdn_to_eeh_dev(pdn);
> + int status, i;
> +
> + /* Wait for Transaction Pending bit to be cleared */
> + for (i = 0; i < 4; i++) {
> + eeh_ops->read_config(pdn, pos, 2, &status);
gcc should have complained on using uninitialized @status here.
> + if (!(status & mask))
> + return;
> +
> + msleep((1 << i) * 100);
> + }
> +
> + pr_warn("%s: Pending transaction while issuing %s FLR to "
> + "%04x:%02x:%02x.%01x\n",
Do not wrap user-visible strings.
> + __func__, af_flr_rst ? "AF" : "",
> + edev->phb->global_number, pdn->busno,
> + PCI_SLOT(pdn->devfn), PCI_FUNC(pdn->devfn));
> +}
> +
> +static int pnv_eeh_do_flr(struct pci_dn *pdn, int option)
> +{
> + struct eeh_dev *edev = pdn_to_eeh_dev(pdn);
> + u32 reg;
> +
> + if (!edev->pcie_cap)
> + return -ENOTTY;
Can pnv_eeh_do_flr() be really called on a non PCIe device, can we get that
far? WARN_ON_ONCE() may be?
> +
> + eeh_ops->read_config(pdn, edev->pcie_cap + PCI_EXP_DEVCAP, 4, ®);
... and here about uninitialized @reg.
> + if (!(reg & PCI_EXP_DEVCAP_FLR))
> + return -ENOTTY;
> +
> + switch (option) {
> + case EEH_RESET_HOT:
> + case EEH_RESET_FUNDAMENTAL:
> + pnv_eeh_wait_for_pending(pdn, edev->pcie_cap + PCI_EXP_DEVSTA,
> + PCI_EXP_DEVSTA_TRPND, false);
> + eeh_ops->read_config(pdn, edev->pcie_cap + PCI_EXP_DEVCTL,
> + 4, ®);
> + reg |= PCI_EXP_DEVCTL_BCR_FLR;
> + eeh_ops->write_config(pdn, edev->pcie_cap + PCI_EXP_DEVCTL,
> + 4, reg);
> + msleep(EEH_PE_RST_HOLD_TIME);
> + break;
> + case EEH_RESET_DEACTIVATE:
> + eeh_ops->read_config(pdn, edev->pcie_cap + PCI_EXP_DEVCTL,
> + 4, ®);
> + reg &= ~PCI_EXP_DEVCTL_BCR_FLR;
> + eeh_ops->write_config(pdn, edev->pcie_cap + PCI_EXP_DEVCTL,
> + 4, reg);
> + msleep(EEH_PE_RST_SETTLE_TIME);
> + break;
> + }
> +
> + return 0;
> +}
> +
> +static int pnv_eeh_do_af_flr(struct pci_dn *pdn, int option)
> +{
> + struct eeh_dev *edev = pdn_to_eeh_dev(pdn);
> + u32 cap;
> +
> + if (!edev->af_cap)
> + return -ENOTTY;
> +
> + eeh_ops->read_config(pdn, edev->af_cap + PCI_AF_CAP, 1, &cap);
... and here about @cap.
> + if (!(cap & PCI_AF_CAP_TP) || !(cap & PCI_AF_CAP_FLR))
> + return -ENOTTY;
> +
> + switch (option) {
> + case EEH_RESET_HOT:
> + case EEH_RESET_FUNDAMENTAL:
> + /*
> + * Wait for Transaction Pending bit to clear. A word-aligned
> + * test is used, so we use the conrol offset rather than status
> + * and shift the test bit to match.
Why word-aligned (not byte or double word)?
> + */
> + pnv_eeh_wait_for_pending(pdn, edev->af_cap + PCI_AF_CTRL,
> + PCI_AF_STATUS_TP << 8, true);
> + eeh_ops->write_config(pdn, edev->af_cap + PCI_AF_CTRL,
> + 1, PCI_AF_CTRL_FLR);
> + msleep(EEH_PE_RST_HOLD_TIME);
> + break;
> + case EEH_RESET_DEACTIVATE:
> + eeh_ops->write_config(pdn, edev->af_cap + PCI_AF_CTRL, 1, 0);
> + msleep(EEH_PE_RST_SETTLE_TIME);
btw there is an unrelated issue with EEH_PE_RST_SETTLE_TIME which is
defined as 1800 which is A LOT (+250ms from EEH_PE_RST_HOLD_TIME and for
some reason this is actually doubled so there is another reset somewhere).
Booting a guest with 63 VFs takes 6 minutes or so, is there a good reason
for such a huge timeout?
> + break;
> + }
> +
> + return 0;
> +}
> +
> +static int pnv_eeh_reset_vf(struct pci_dn *pdn, int option)
> +{
> + int ret;
> +
> + ret = pnv_eeh_do_flr(pdn, option);
> + if (ret != -ENOTTY)
> + return ret;
> +
> + return pnv_eeh_do_af_flr(pdn, option);
> +}
> +
> +static int pnv_eeh_vf_pe_reset(struct eeh_pe *pe, int option)
> +{
> + struct eeh_dev *edev, *tmp;
> + struct pci_dn *pdn;
> + int ret;
> +
> + eeh_pe_for_each_dev(pe, edev, tmp) {
> + pdn = eeh_dev_to_pdn(edev);
> + ret = pnv_eeh_reset_vf(pdn, option);
> + if (ret)
> + return ret;
> + }
> +
> + return 0;
> +}
> +
> void pnv_pci_reset_secondary_bus(struct pci_dev *dev)
> {
> struct pci_controller *hose;
> @@ -968,7 +1090,9 @@ static int pnv_eeh_reset(struct eeh_pe *pe, int option)
> }
>
> bus = eeh_pe_bus_get(pe);
> - if (pci_is_root_bus(bus) ||
> + if (pe->type & EEH_PE_VF)
> + ret = pnv_eeh_vf_pe_reset(pe, option);
> + else if (pci_is_root_bus(bus) ||
> pci_is_root_bus(bus->parent))
> ret = pnv_eeh_root_reset(hose, option);
> else
> @@ -1108,6 +1232,14 @@ static inline bool pnv_eeh_cfg_blocked(struct pci_dn *pdn)
> if (!edev || !edev->pe)
> return false;
>
> + /*
> + * We will issue FLR or AF FLR to all VFs, which are contained
> + * in VF PE. It relies on the EEH PCI config accessors. So we
> + * can't block them during the window.
> + */
> + if ((edev->physfn) && (edev->pe->state & EEH_PE_RESET))
Extra braces around edev->physfn.
> + return false;
> +
> if (edev->pe->state & EEH_PE_CFG_BLOCKED)
> return true;
>
>
--
Alexey
next prev parent reply other threads:[~2015-10-30 4:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 3:15 [PATCH V10 00/12] VF EEH on Power8 Wei Yang
2015-10-26 3:15 ` [PATCH V10 01/12] PCI/IOV: Rename and export virtfn_add/virtfn_remove Wei Yang
2015-10-27 1:31 ` Andrew Donnellan
2015-10-27 23:06 ` Bjorn Helgaas
2015-10-28 1:21 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 02/12] PCI: Add pcibios_bus_add_device() weak function Wei Yang
2015-10-27 5:07 ` Andrew Donnellan
2015-10-26 3:15 ` [PATCH V10 03/12] powerpc/pci: Cache VF index in pci_dn Wei Yang
2015-10-27 5:01 ` Andrew Donnellan
2015-10-27 22:04 ` Daniel Axtens
2015-10-28 1:45 ` Wei Yang
2015-10-30 2:05 ` Alexey Kardashevskiy
2015-10-30 2:48 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 04/12] powerpc/pci: Remove VFs prior to PF Wei Yang
2015-10-30 3:04 ` Alexey Kardashevskiy
2015-10-30 6:31 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 05/12] powerpc/eeh: Cache only BARs, not windows or IOV BARs Wei Yang
2015-10-29 3:29 ` Daniel Axtens
2015-10-29 8:57 ` Wei Yang
2015-10-30 3:22 ` Alexey Kardashevskiy
2015-10-30 6:37 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 06/12] powerpc/powernv: EEH device for VF Wei Yang
2015-10-30 3:33 ` Alexey Kardashevskiy
2015-10-30 6:52 ` Wei Yang
2015-10-30 7:36 ` Alexey Kardashevskiy
2015-10-30 7:58 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 07/12] powerpc/eeh: Create PE for VFs Wei Yang
2015-10-30 3:46 ` Alexey Kardashevskiy
2015-10-30 6:59 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 08/12] powerpc/powernv: Support EEH reset for VF PE Wei Yang
2015-10-30 4:11 ` Alexey Kardashevskiy [this message]
2015-10-30 7:18 ` Wei Yang
2015-10-30 8:05 ` Alexey Kardashevskiy
2015-11-02 22:45 ` Wei Yang
2015-10-26 3:15 ` [PATCH V10 09/12] powerpc/powernv: Support PCI config restore for VFs Wei Yang
2015-10-30 4:56 ` Alexey Kardashevskiy
2015-10-30 8:17 ` Wei Yang
2015-10-26 3:16 ` [PATCH V10 10/12] powerpc/eeh: Support error recovery for VF PE Wei Yang
2015-10-30 5:20 ` Alexey Kardashevskiy
2015-11-01 1:53 ` Wei Yang
2015-11-01 23:40 ` Alexey Kardashevskiy
2015-11-02 9:39 ` Wei Yang
2015-10-26 3:16 ` [PATCH V10 11/12] powerpc/eeh: Don't block PCI config on resetting " Wei Yang
2015-10-30 5:42 ` Alexey Kardashevskiy
2015-10-30 7:19 ` Wei Yang
2015-10-26 3:16 ` [PATCH V10 12/12] powerpc/eeh: Handle hot removed VF when PF is EEH aware Wei Yang
2015-10-30 5:35 ` Alexey Kardashevskiy
2015-10-30 7:29 ` Wei Yang
2015-10-27 23:11 ` [PATCH V10 00/12] VF EEH on Power8 Bjorn Helgaas
2015-10-28 1:50 ` Wei Yang
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=5632EDE8.2010601@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=weiyang@linux.vnet.ibm.com \
/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).