Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp676514ybe; Fri, 13 Sep 2019 04:34:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqw38AMF5v14xJiD56tx9nyvQd/MITZkICW/yDdM7M3KOkjaPHBrwpezrN1k7t6lTeEksyN5 X-Received: by 2002:a17:906:4882:: with SMTP id v2mr39507841ejq.100.1568374446826; Fri, 13 Sep 2019 04:34:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568374446; cv=none; d=google.com; s=arc-20160816; b=wE3iaZa+vJAfxipS7GSG94b7iqfVIi7+tp4qDg8R2PTz51cndRk40QWxti3ZFdnoN+ 0eUUIRvdI7T5zJEFJ1Shx+QJeNqANBNrY9hes+yk8XB2SISDAUkCmpNFxRI30motk/sR RqZBhOn2p2AJ8LtMQWrE6xjQxnYy7CLY5m+lEQW6Dc85sao0McXtG5PqJSWly2a6Ed83 EFhQ/cheKAHBEUsdEWLyRLBcFqgpK8m9KBbSqRAzIdvxCa6u/wxBc8Fic7K0ntkS1Nty E9Krjn9xXL8ln8jFkVMYYmHUp0XKLnDrXVHs2wfTS5XXrFkGh3IRZepaLNbvzN4YDuzJ Ns+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=JvG2VxG/MSZ23BEkQ2KDjAnn1y2OiH2fWtbR0aS2Ft0=; b=JlL08KgPcHbqlbpHmuMiTxM9aRFLk5bSgfXjEfOnleCggVd5RlYpRTc7f7aNId6085 233Hai2a92gNAzMoI2yMOtteUEAHZvP5+NCXkyH2CnmOuBc4hXiCkG5BPRmOaXkdfwBW guIbOD2lKzGRgSoybovnV8eAmdG0yOdfc089w+OGDXitnzQYYgUiMeBBs2xbH/WWUVNl NZ3JfHe2VYkEQmV0fAhBRiRF50PoiL6NwoSTA0iEWgV0TSE3f5lwpew52vUmXX8JnqoH 7jCqfONNLsVyMUDXdktoe+iYqBNVnFBNVVc3NYfYsr/83DZJLJkSrjyLqfrGUBnnECqS 8j/Q== 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 mj26si14142589ejb.203.2019.09.13.04.33.43; Fri, 13 Sep 2019 04:34:06 -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 S2387413AbfIML2t (ORCPT + 99 others); Fri, 13 Sep 2019 07:28:49 -0400 Received: from foss.arm.com ([217.140.110.172]:41924 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726266AbfIML2t (ORCPT ); Fri, 13 Sep 2019 07:28:49 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 301F828; Fri, 13 Sep 2019 04:28:48 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (unknown [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id DFE3A3F59C; Fri, 13 Sep 2019 04:28:45 -0700 (PDT) Date: Fri, 13 Sep 2019 12:28:41 +0100 From: Lorenzo Pieralisi To: Jonathan Chocron , bhelgaas@google.com Cc: jingoohan1@gmail.com, gustavo.pimentel@synopsys.com, robh+dt@kernel.org, mark.rutland@arm.com, andrew.murray@arm.com, dwmw@amazon.co.uk, benh@kernel.crashing.org, alisaidi@amazon.com, ronenk@amazon.com, barakw@amazon.com, talel@amazon.com, hanochu@amazon.com, hhhawa@amazon.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v6 4/7] PCI: Add quirk to disable MSI-X support for Amazon's Annapurna Labs Root Port Message-ID: <20190913112841.GA8153@e121166-lin.cambridge.arm.com> References: <20190912130042.14597-1-jonnyc@amazon.com> <20190912130042.14597-5-jonnyc@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190912130042.14597-5-jonnyc@amazon.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 12, 2019 at 04:00:42PM +0300, Jonathan Chocron wrote: > The Root Port (identified by [1c36:0031]) doesn't support MSI-X. On some > platforms it is configured to not advertise the capability at all, while > on others it (mistakenly) does. This causes a panic during > initialization by the pcieport driver, since it tries to configure the > MSI-X capability. Specifically, when trying to access the MSI-X table > a "non-existing addr" exception occurs. > > Example stacktrace snippet: > > SError Interrupt on CPU2, code 0xbf000000 -- SError > CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.2.0-rc1-Jonny-14847-ge76f1d4a1828-dirty #33 > Hardware name: Annapurna Labs Alpine V3 EVP (DT) > pstate: 80000005 (Nzcv daif -PAN -UAO) > pc : __pci_enable_msix_range+0x4e4/0x608 > lr : __pci_enable_msix_range+0x498/0x608 > sp : ffffff80117db700 > x29: ffffff80117db700 x28: 0000000000000001 > x27: 0000000000000001 x26: 0000000000000000 > x25: ffffffd3e9d8c0b0 x24: 0000000000000000 > x23: 0000000000000000 x22: 0000000000000000 > x21: 0000000000000001 x20: 0000000000000000 > x19: ffffffd3e9d8c000 x18: ffffffffffffffff > x17: 0000000000000000 x16: 0000000000000000 > x15: ffffff80116496c8 x14: ffffffd3e9844503 > x13: ffffffd3e9844502 x12: 0000000000000038 > x11: ffffffffffffff00 x10: 0000000000000040 > x9 : ffffff801165e270 x8 : ffffff801165e268 > x7 : 0000000000000002 x6 : 00000000000000b2 > x5 : ffffffd3e9d8c2c0 x4 : 0000000000000000 > x3 : 0000000000000000 x2 : 0000000000000000 > x1 : 0000000000000000 x0 : ffffffd3e9844680 > Kernel panic - not syncing: Asynchronous SError Interrupt > CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.2.0-rc1-Jonny-14847-ge76f1d4a1828-dirty #33 > Hardware name: Annapurna Labs Alpine V3 EVP (DT) > Call trace: > dump_backtrace+0x0/0x140 > show_stack+0x14/0x20 > dump_stack+0xa8/0xcc > panic+0x140/0x334 > nmi_panic+0x6c/0x70 > arm64_serror_panic+0x74/0x88 > __pte_error+0x0/0x28 > el1_error+0x84/0xf8 > __pci_enable_msix_range+0x4e4/0x608 > pci_alloc_irq_vectors_affinity+0xdc/0x150 > pcie_port_device_register+0x2b8/0x4e0 > pcie_portdrv_probe+0x34/0xf0 > > Notice that this quirk also disables MSI (which may work, but hasn't > been tested nor has a current use case), since currently there is no > standard way to disable only MSI-X. > > Signed-off-by: Jonathan Chocron > Reviewed-by: Gustavo Pimentel > Reviewed-by: Andrew Murray > --- > drivers/pci/quirks.c | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) I will prepare this series for upstream but I would like to have Bjorn's ACK before pushing it out since you updated this patch following his review. Thanks, Lorenzo > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c > index 2e983f2a0ee9..c1077e806291 100644 > --- a/drivers/pci/quirks.c > +++ b/drivers/pci/quirks.c > @@ -2977,6 +2977,24 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATTANSIC, 0x10a1, > quirk_msi_intx_disable_qca_bug); > DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_ATTANSIC, 0xe091, > quirk_msi_intx_disable_qca_bug); > + > +/* > + * Amazon's Annapurna Labs 1c36:0031 Root Ports don't support MSI-X, so it > + * should be disabled on platforms where the device (mistakenly) advertises it. > + * > + * Notice that this quirk also disables MSI (which may work, but hasn't been > + * tested), since currently there is no standard way to disable only MSI-X. > + * > + * The 0031 device id is reused for other non Root Port device types, > + * therefore the quirk is registered for the PCI_CLASS_BRIDGE_PCI class. > + */ > +static void quirk_al_msi_disable(struct pci_dev *dev) > +{ > + dev->no_msi = 1; > + pci_warn(dev, "Disabling MSI/MSI-X\n"); > +} > +DECLARE_PCI_FIXUP_CLASS_FINAL(PCI_VENDOR_ID_AMAZON_ANNAPURNA_LABS, 0x0031, > + PCI_CLASS_BRIDGE_PCI, 8, quirk_al_msi_disable); > #endif /* CONFIG_PCI_MSI */ > > /* > -- > 2.17.1 >