Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp640837ybl; Thu, 22 Aug 2019 02:34:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqwsQVUHSLC+NLGKLqAy+6GWdpSnGFmj5A0tZ0tkF/vp97uXNZtPsmaafTjSG+KNkJU5KID0 X-Received: by 2002:a17:90a:2e86:: with SMTP id r6mr4380562pjd.67.1566466464817; Thu, 22 Aug 2019 02:34:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566466464; cv=none; d=google.com; s=arc-20160816; b=ukK8Qx63xr+G1Rt9qnG6cFZQI5jaX5dPXF/ifdTS68QUuP8AF1x4HKlr7LJFYsRQgM q/K0H9u07XgsRlKSxZViL9yk5p1o6xo8XkYWpFN9jNN6c8hcefy5+70tMO9GYq/jASTX szIQ25hO5d7rvr9m3ydefHYM8IsGoIr7qhNc1zf6UlB5xTpGJUGWMkc/cW53NI85c0lk LIur76xP1VIVQuD5KO+0jTYB7ZFXaIqTzkYrgQrmVimdmBgqYF1xOfp3DuAjT4wosrxS IzVz5VtDBQY6wiLHh+kihCE3ye5trpXuyR6rnvDBpr07B9Br8pOc+mw/VDAfSkzvPt/9 JWmA== 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=BsBcaxxyAoxoV/i7L+YKU1kmPX+vhA95B0m0C0GQQNI=; b=MpG8NKOHyoWkxgocUYjRoDRDio3r0xafxe85XGzOEUrxT2BGoAkPSnOEflubnKnbGp AwloIqddsmLW+D2P5QTC3vMhpfgPehChoYimJmELU/VKs+IvBd65S1t0B7mUffv3jeEF JLMhTeGK0vpKWDtucnlIngXpaYeoT+OKQqLD/rVt4/8Mi3Or7G21rxPzvnbxpcy0aC1Y BqPyRFcFNtr10dHelS0XSOEDmLRg9xnVDIRBotCHQeo1DukfyCCO8h1K2Zow52XmFwv7 j++7JV5C8EfENbHeRAn9+d6k+KzjY0j8bnQMM4USRsryjvNzyw+SObQA8c5z34zCeWcv j/5w== 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 bi12si16617243plb.231.2019.08.22.02.34.08; Thu, 22 Aug 2019 02:34:24 -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 S1731742AbfHVHyN (ORCPT + 99 others); Thu, 22 Aug 2019 03:54:13 -0400 Received: from foss.arm.com ([217.140.110.172]:40530 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726197AbfHVHyN (ORCPT ); Thu, 22 Aug 2019 03:54:13 -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 5216E344; Thu, 22 Aug 2019 00:54:12 -0700 (PDT) Received: from localhost (unknown [10.37.6.20]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9E94F3F706; Thu, 22 Aug 2019 00:54:11 -0700 (PDT) Date: Thu, 22 Aug 2019 08:54:10 +0100 From: Andrew Murray To: Jonathan Chocron Cc: lorenzo.pieralisi@arm.com, bhelgaas@google.com, jingoohan1@gmail.com, gustavo.pimentel@synopsys.com, robh+dt@kernel.org, mark.rutland@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 v4 4/7] PCI: Add quirk to disable MSI-X support for Amazon's Annapurna Labs Root Port Message-ID: <20190822075409.GK23903@e119886-lin.cambridge.arm.com> References: <20190821153545.17635-1-jonnyc@amazon.com> <20190821153545.17635-5-jonnyc@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190821153545.17635-5-jonnyc@amazon.com> User-Agent: Mutt/1.10.1+81 (426a6c1) (2018-08-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 21, 2019 at 06:35:44PM +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: > > [ 1.632363] SError Interrupt on CPU2, code 0xbf000000 -- SError > [ 1.632364] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.2.0-rc1-Jonny-14847-ge76f1d4a1828-dirty #33 > [ 1.632365] Hardware name: Annapurna Labs Alpine V3 EVP (DT) > [ 1.632365] pstate: 80000005 (Nzcv daif -PAN -UAO) > [ 1.632366] pc : __pci_enable_msix_range+0x4e4/0x608 > [ 1.632367] lr : __pci_enable_msix_range+0x498/0x608 > [ 1.632367] sp : ffffff80117db700 > [ 1.632368] x29: ffffff80117db700 x28: 0000000000000001 > [ 1.632370] x27: 0000000000000001 x26: 0000000000000000 > [ 1.632372] x25: ffffffd3e9d8c0b0 x24: 0000000000000000 > [ 1.632373] x23: 0000000000000000 x22: 0000000000000000 > [ 1.632375] x21: 0000000000000001 x20: 0000000000000000 > [ 1.632376] x19: ffffffd3e9d8c000 x18: ffffffffffffffff > [ 1.632378] x17: 0000000000000000 x16: 0000000000000000 > [ 1.632379] x15: ffffff80116496c8 x14: ffffffd3e9844503 > [ 1.632380] x13: ffffffd3e9844502 x12: 0000000000000038 > [ 1.632382] x11: ffffffffffffff00 x10: 0000000000000040 > [ 1.632384] x9 : ffffff801165e270 x8 : ffffff801165e268 > [ 1.632385] x7 : 0000000000000002 x6 : 00000000000000b2 > [ 1.632387] x5 : ffffffd3e9d8c2c0 x4 : 0000000000000000 > [ 1.632388] x3 : 0000000000000000 x2 : 0000000000000000 > [ 1.632390] x1 : 0000000000000000 x0 : ffffffd3e9844680 > [ 1.632392] Kernel panic - not syncing: Asynchronous SError Interrupt > [ 1.632393] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.2.0-rc1-Jonny-14847-ge76f1d4a1828-dirty #33 > [ 1.632394] Hardware name: Annapurna Labs Alpine V3 EVP (DT) > [ 1.632394] Call trace: > [ 1.632395] dump_backtrace+0x0/0x140 > [ 1.632395] show_stack+0x14/0x20 > [ 1.632396] dump_stack+0xa8/0xcc > [ 1.632396] panic+0x140/0x334 > [ 1.632397] nmi_panic+0x6c/0x70 > [ 1.632398] arm64_serror_panic+0x74/0x88 > [ 1.632398] __pte_error+0x0/0x28 > [ 1.632399] el1_error+0x84/0xf8 > [ 1.632400] __pci_enable_msix_range+0x4e4/0x608 > [ 1.632400] pci_alloc_irq_vectors_affinity+0xdc/0x150 > [ 1.632401] pcie_port_device_register+0x2b8/0x4e0 > [ 1.632402] 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 > --- > drivers/pci/quirks.c | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c > index 23672680dba7..b6e6e7df3f7b 100644 > --- a/drivers/pci/quirks.c > +++ b/drivers/pci/quirks.c > @@ -2925,6 +2925,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. Thanks for adding this. Reviewed-by: Andrew Murray > + * > + * 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 >