Received: by 10.223.176.46 with SMTP id f43csp2803396wra; Mon, 22 Jan 2018 03:45:54 -0800 (PST) X-Google-Smtp-Source: AH8x227GJxHKtwknOn3M1DNk9peKbsXnIPQRaydo2rnlcKSt2lRPHBQ8DB2/zdPXrj02QpV96fQW X-Received: by 10.98.69.82 with SMTP id s79mr8178781pfa.214.1516621554168; Mon, 22 Jan 2018 03:45:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516621554; cv=none; d=google.com; s=arc-20160816; b=D4RhmPhUaXcEWPSYZMNr2Wbtze90AE4ioBr9BDHENeV23z3xeOhYV+nLrro35NuTtY yWDa7qmC+LzrEBd8W8OQV1TdZN1odpCLUBWyZMaEFPmnT4Jhi+gNA+Aob2YcRgUIFz6G +5Z3gVzr8LM5s/+mwbc0oznVZ309ETwaddMfDDLe52Sl4BmXDXaWi+Bu7hFar/ZyjYU+ SOwed+ReYp2/Tz4LQnPelGN8xQ1xyaLuf6OF8l81LpHC9n4U5k9VP4B28Tk4TaGszY6l 55Uy9c0nabHrWJ2v4x9Eqd2Gyel20mU19KnD5SK7lVoCtUAMyi0e0M8gT9swgVDSdukk 4y2Q== 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:organization:from:references:cc:to:subject :arc-authentication-results; bh=ZHDKY8MTOq1XNdYPJ1/iFPWiJJS1NZ+hCoLdPY3cq3Y=; b=TRjysWiS0nMBMdGtCUpOpqRvS7+XHFg0nb5zh9GTzhameOycJqeqpuv79LUn3/o4C1 REnr18rxMi8vaLlh/WdYIPc3UgAgGb9hw3kOofegwBmnDCVpGazLwRLTOP9qWSd2PptH UsJf+qns5PLcIlk/Jd+Q6BzHRG4pwwrm4seYj+Ux7nafURHSUe8lBGVsGuFg8pYpPYlZ Hm8ws9m4OBGiFswM7r9uOXO+7sC54UA0pCHJyyBB82pmKI9ABpHOfjKY+X7SUaKXxr1g gE2npiVj/uiJg2KVqyF1knWFvmR7RcLwRm3hpfFFvGJTUJuTxidOX4R/fpAG0z+6LI/u NThw== 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 m184si56743pfb.373.2018.01.22.03.45.39; Mon, 22 Jan 2018 03:45:54 -0800 (PST) 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 S1751121AbeAVLpS (ORCPT + 99 others); Mon, 22 Jan 2018 06:45:18 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:57610 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750886AbeAVLpR (ORCPT ); Mon, 22 Jan 2018 06:45:17 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 3D73D1529; Mon, 22 Jan 2018 03:45:17 -0800 (PST) Received: from [10.1.207.62] (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D34203F53D; Mon, 22 Jan 2018 03:45:15 -0800 (PST) Subject: Re: [PATCH v2] iommu/arm-smmu-v3: limit reporting of MSI allocation failures To: Nate Watterson , Will Deacon , Robin Murphy , Joerg Roedel , linux-arm-kernel@lists.infradead.org, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Cc: Sinan Kaya References: <1516471684-25052-1-git-send-email-nwatters@codeaurora.org> From: Marc Zyngier Organization: ARM Ltd Message-ID: <39eee30e-1298-24d5-926b-9cd7fe532e59@arm.com> Date: Mon, 22 Jan 2018 11:45:14 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1516471684-25052-1-git-send-email-nwatters@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/01/18 18:08, Nate Watterson wrote: > Currently, the arm-smmu-v3 driver expects to allocate MSIs for all SMMUs > with FEAT_MSI set. This results in unwarranted "failed to allocate MSIs" > warnings being printed on systems where FW was either deliberately > configured to force the use of SMMU wired interrupts -or- is altogether > incapable of describing SMMU MSI topology (ACPI IORT prior to rev.C). > > Remedy this by checking msi_domain before attempting to allocate SMMU > MSIs. > > Signed-off-by: Nate Watterson > Signed-off-by: Sinan Kaya > --- > drivers/iommu/arm-smmu-v3.c | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c > index 744592d..00de028 100644 > --- a/drivers/iommu/arm-smmu-v3.c > +++ b/drivers/iommu/arm-smmu-v3.c > @@ -2328,10 +2328,15 @@ static void arm_smmu_setup_msis(struct arm_smmu_device *smmu) > if (!(smmu->features & ARM_SMMU_FEAT_MSI)) > return; > > + if (!dev->msi_domain) { > + dev_info(smmu->dev, "msi_domain absent - falling back to wired irqs\n"); > + return; > + } > + > /* Allocate MSIs for evtq, gerror and priq. Ignore cmdq */ > ret = platform_msi_domain_alloc_irqs(dev, nvec, arm_smmu_write_msi_msg); > if (ret) { > - dev_warn(dev, "failed to allocate MSIs\n"); > + dev_warn(dev, "failed to allocate MSIs - falling back to wired irqs\n"); > return; > } > > Acked-by: Marc Zyngier M. -- Jazz is not dead. It just smells funny...