Received: by 10.192.165.148 with SMTP id m20csp1919817imm; Sun, 6 May 2018 02:35:40 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpCiZCTGMvepPSz4QCY2yEFanIOKvuaSyAy87v33SvkuRqKbyRNqP9QNVyQsxKj+ADOuCQz X-Received: by 10.98.86.16 with SMTP id k16mr32769097pfb.19.1525599339994; Sun, 06 May 2018 02:35:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525599339; cv=none; d=google.com; s=arc-20160816; b=PnrRQ3Yzb6GrvYASlud1eKJgKygMBUfElIcXHTsDGewcwJKgka2qF73+cJY/lQmyYK Xq3c2y7Iz1aaWG7GNIpjOPS/HUPOIfZydQBAU4uzDm83oF5UI3CERfc4obf102PyOrEy BKYboOpIpmKlZ6+vq6E8PSLYUf60CGPMvT2SY2to78C35d/SBTMz3GzuwBx9e2tPoVYl ckTHCR/AOL3Y6wLKNcrt5DRZ9wqV5pxUiIeNQcQEbofq8v4PYJqYrZDIa4oYgETWWFfD nS6vo5dSOgUfINui8WNsL6ky7hLSfVlsWsz7NXepxmfrYYGIN1ehNSzkNXfYfW8VCBPA KbBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=kOUT3YxAF0NdcQiR8c+3ok5h3EM0CIwPlOihweTyMKE=; b=rI024wqgThMotSKVs3qZsN4Tc2j52ZwuOEoVvxeX8cXPq71NgrXgOPpPBRK24ViSQg kxBNODrqxdt+I63S+D2wUexZpvR4Cyi0uNPhir1f/Au4VSVBF2TW+cZ6Y+gWJJq/naFY GKTGT7lYV6al7i5jgx8Nc/JxORPYqM7+Yiu9l4rBQuEvKfx48o/YXJ8LJ/qjMQ9ZUk9e PKDiCE1nIakmiTzTgGvkdV/XD4i5jQUfhVZ2YJa0Wg8VhMkcXydzkIsR9nyzLX0NlHjF rpoKpJtgjhFt+QV+Z93BKIG/lnxABvXyzpKY2kVgJBbm2f83/VCFx5gHywQuFmY3O58+ 5NXA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b8-v6si1897048plz.469.2018.05.06.02.35.25; Sun, 06 May 2018 02:35:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751796AbeEFJfH (ORCPT + 99 others); Sun, 6 May 2018 05:35:07 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:33673 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751187AbeEFJfE (ORCPT ); Sun, 6 May 2018 05:35:04 -0400 Received: from [192.168.0.3] (ip5f5aec93.dynamic.kabel-deutschland.de [95.90.236.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id C6C782012BA054; Sun, 6 May 2018 11:35:01 +0200 (CEST) Subject: Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago) To: Bjorn Helgaas Cc: okaya@codeaurora.org, Pavel Machek , Bjorn Helgaas , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Wunner References: <8770820b-85a0-172b-7230-3a44524e6c9f@molgen.mpg.de> <20180427192207.GG8199@bhelgaas-glaptop.roam.corp.google.com> <43b8ab4a-f8ee-dc96-40ec-e6fdfedd8309@molgen.mpg.de> <20180504024527.GE15790@bhelgaas-glaptop.roam.corp.google.com> <20180504133327.GF15790@bhelgaas-glaptop.roam.corp.google.com> From: Paul Menzel Message-ID: Date: Sun, 6 May 2018 11:35:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180504133327.GF15790@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Bjorn, Am 04.05.2018 um 15:33 schrieb Bjorn Helgaas: […] > Yes, definitely. I intended to do that but got a little lazy. What > do you think about the following? Paul, if you haven't tested the > first patch, can you try this one instead? The logic is pretty much > the same. > > 3461a068661c ("PCI: pciehp: Wait for hotplug command completion > lazily") mentions AMD and Nvidia devices with the same issue, but > unfortunately doesn't include any specifics. > > > commit b0d6f2230e12c85ae3b65a854a53c67c7c1f6406 > Author: Bjorn Helgaas > Date: Thu May 3 18:39:38 2018 -0500 > > PCI: pciehp: Add quirk for Intel Command Completed erratum > > The Intel CF118 erratum means the controller does not set the Command > Completed bit unless writes to the Slot Command register change "Control" > bits. Command Completed is never set for writes that only change software > notification "Enable" bits. This results in timeouts like this: > > pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago) > > When this erratum is present, avoid these timeouts by marking commands > "completed" immediately unless they change the "Control" bits. > > Here's the text of the erratum from the Intel document: > > CF118 PCIe Slot Status Register Command Completed bit not always > updated on any configuration write to the Slot Control > Register > > Problem: For PCIe root ports (devices 0 - 10) supporting hot-plug, > the Slot Status Register (offset AAh) Command Completed > (bit[4]) status is updated under the following condition: > IOH will set Command Completed bit after delivering the new > commands written in the Slot Controller register (offset > A8h) to VPP. The IOH detects new commands written in Slot > Control register by checking the change of value for Power > Controller Control (bit[10]), Power Indicator Control > (bits[9:8]), Attention Indicator Control (bits[7:6]), or > Electromechanical Interlock Control (bit[11]) fields. Any > other configuration writes to the Slot Control register > without changing the values of these fields will not cause > Command Completed bit to be set. > > The PCIe Base Specification Revision 2.0 or later describes > the “Slot Control Register” in section 7.8.10, as follows > (Reference section 7.8.10, Slot Control Register, Offset > 18h). In hot-plug capable Downstream Ports, a write to the > Slot Control register must cause a hot-plug command to be > generated (see Section 6.7.3.2 for details on hot-plug > commands). A write to the Slot Control register in a > Downstream Port that is not hotplug capable must not cause a > hot-plug command to be executed. > > The PCIe Spec intended that every write to the Slot Control > Register is a command and expected a command complete status > to abstract the VPP implementation specific nuances from the > OS software. IOH PCIe Slot Control Register implementation > is not fully conforming to the PCIe Specification in this > respect. > > Implication: Software checking on the Command Completed status after > writing to the Slot Control register may time out. > > Workaround: Software can read the Slot Control register and compare the > existing and new values to determine if it should check the > Command Completed status after writing to the Slot Control > register. > > Link: http://www.intel.com/content/www/us/en/processors/xeon/xeon-e7-v2-spec-update.html > Link: https://lkml.kernel.org/r/8770820b-85a0-172b-7230-3a44524e6c9f@molgen.mpg.de > Reported-by: Paul Menzel > Signed-off-by: Bjorn Helgaas > > diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c > index 18a42f8f5dc5..e70eba5ea906 100644 > --- a/drivers/pci/hotplug/pciehp_hpc.c > +++ b/drivers/pci/hotplug/pciehp_hpc.c > @@ -10,7 +10,6 @@ > * All rights reserved. > * > * Send feedback to , > - * > */ > > #include > @@ -147,25 +146,22 @@ static void pcie_wait_cmd(struct controller *ctrl) > else > rc = pcie_poll_cmd(ctrl, jiffies_to_msecs(timeout)); > > - /* > - * Controllers with errata like Intel CF118 don't generate > - * completion notifications unless the power/indicator/interlock > - * control bits are changed. On such controllers, we'll emit this > - * timeout message when we wait for completion of commands that > - * don't change those bits, e.g., commands that merely enable > - * interrupts. > - */ > if (!rc) > ctrl_info(ctrl, "Timeout on hotplug command %#06x (issued %u msec ago)\n", > ctrl->slot_ctrl, > jiffies_to_msecs(jiffies - ctrl->cmd_started)); > } > > +#define CC_ERRATUM_MASK (PCI_EXP_SLTCTL_PCC | \ > + PCI_EXP_SLTCTL_PIC | \ > + PCI_EXP_SLTCTL_AIC | \ > + PCI_EXP_SLTCTL_EIC) > + > static void pcie_do_write_cmd(struct controller *ctrl, u16 cmd, > u16 mask, bool wait) > { > struct pci_dev *pdev = ctrl_dev(ctrl); > - u16 slot_ctrl; > + u16 slot_ctrl_orig, slot_ctrl; > > mutex_lock(&ctrl->ctrl_lock); > > @@ -180,6 +176,7 @@ static void pcie_do_write_cmd(struct controller *ctrl, u16 cmd, > goto out; > } > > + slot_ctrl_orig = slot_ctrl; > slot_ctrl &= ~mask; > slot_ctrl |= (cmd & mask); > ctrl->cmd_busy = 1; > @@ -188,6 +185,17 @@ static void pcie_do_write_cmd(struct controller *ctrl, u16 cmd, > ctrl->cmd_started = jiffies; > ctrl->slot_ctrl = slot_ctrl; > > + /* > + * Controllers with the Intel CF118 and similar errata advertise > + * Command Completed support, but they only set Command Completed > + * if we change the "Control" bits for power, power indicator, > + * attention indicator, or interlock. If we only change the > + * "Enable" bits, they never set the Command Completed bit. > + */ > + if (pdev->broken_cmd_compl && > + (slot_ctrl_orig & CC_ERRATUM_MASK) == (slot_ctrl & CC_ERRATUM_MASK)) > + ctrl->cmd_busy = 0; > + > /* > * Optionally wait for the hardware to be ready for a new command, > * indicating completion of the above issued command. > @@ -861,7 +869,7 @@ struct controller *pcie_init(struct pcie_device *dev) > PCI_EXP_SLTSTA_MRLSC | PCI_EXP_SLTSTA_CC | > PCI_EXP_SLTSTA_DLLSC); > > - ctrl_info(ctrl, "Slot #%d AttnBtn%c PwrCtrl%c MRL%c AttnInd%c PwrInd%c HotPlug%c Surprise%c Interlock%c NoCompl%c LLActRep%c\n", > + ctrl_info(ctrl, "Slot #%d AttnBtn%c PwrCtrl%c MRL%c AttnInd%c PwrInd%c HotPlug%c Surprise%c Interlock%c NoCompl%c LLActRep%c%s\n", > (slot_cap & PCI_EXP_SLTCAP_PSN) >> 19, > FLAG(slot_cap, PCI_EXP_SLTCAP_ABP), > FLAG(slot_cap, PCI_EXP_SLTCAP_PCP), > @@ -872,7 +880,8 @@ struct controller *pcie_init(struct pcie_device *dev) > FLAG(slot_cap, PCI_EXP_SLTCAP_HPS), > FLAG(slot_cap, PCI_EXP_SLTCAP_EIP), > FLAG(slot_cap, PCI_EXP_SLTCAP_NCCS), > - FLAG(link_cap, PCI_EXP_LNKCAP_DLLLARC)); > + FLAG(link_cap, PCI_EXP_LNKCAP_DLLLARC), > + pdev->broken_cmd_compl ? " (with Cmd Compl erratum)" : ""); > > if (pcie_init_slot(ctrl)) > goto abort_ctrl; > @@ -891,3 +900,17 @@ void pciehp_release_ctrl(struct controller *ctrl) > pcie_cleanup_slot(ctrl); > kfree(ctrl); > } > + > +static void quirk_cmd_compl(struct pci_dev *pdev) > +{ > + u32 slot_cap; > + > + if (pci_is_pcie(pdev)) { > + pcie_capability_read_dword(pdev, PCI_EXP_SLTCAP, &slot_cap); > + if (slot_cap & PCI_EXP_SLTCAP_HPC && > + !(slot_cap & PCI_EXP_SLTCAP_NCCS)) > + pdev->broken_cmd_compl = 1; > + } > +} > +DECLARE_PCI_FIXUP_CLASS_EARLY(PCI_VENDOR_ID_INTEL, PCI_ANY_ID, > + PCI_CLASS_BRIDGE_PCI, 8, quirk_cmd_compl); > diff --git a/include/linux/pci.h b/include/linux/pci.h > index 73178a2fcee0..60cb5350ad28 100644 > --- a/include/linux/pci.h > +++ b/include/linux/pci.h > @@ -406,6 +406,9 @@ struct pci_dev { > struct bin_attribute *res_attr[DEVICE_COUNT_RESOURCE]; /* sysfs file for resources */ > struct bin_attribute *res_attr_wc[DEVICE_COUNT_RESOURCE]; /* sysfs file for WC mapping of resources */ > > +#ifdef CONFIG_HOTPLUG_PCI_PCIE > + unsigned int broken_cmd_compl:1; /* Command Complete broken */ > +#endif > #ifdef CONFIG_PCIE_PTM > unsigned int ptm_root:1; > unsigned int ptm_enabled:1; > With this change, the message is also not shown anymore on the Lenovo X60. Thank you. Tested-by: Paul Menzel Kind regards, Paul