Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2830187ybk; Mon, 18 May 2020 08:56:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJypCYHstIph8OvP1+Si4vz5KLgnOivGgV58oJLJqPqEvVjvWqoV0UCPUzYQHTiiQNrmWNf/ X-Received: by 2002:a17:906:41a:: with SMTP id d26mr14864735eja.217.1589817385032; Mon, 18 May 2020 08:56:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589817385; cv=none; d=google.com; s=arc-20160816; b=vjKGVcIM1ynZTF6bD4KxsFLEoaERlhW8aHur2vVfmEUwyMw9HIJSMsGS8Pc5LVJdGg YIP2zN5DPByeEpuuxJkR2fVsKh8TJSV4PBdNGjObeweE1hhe3AxfysereZsNoIkXOmKe WKY9go3aOyYxUP1+omCoxJQcH6lHa7dTM7QpBTzdgqbwbhzVVeQXxUVHQGjLB4+Q5nl+ AOR9rx+B4re3ZghID1/S801HmpyyZ4D+BivVfuJ7gi7nIL+bEQuufZeL3vJgOuqSGQJm ZvYFsEQFFWFR9yLCe1nhEbxoqP31ii1yT35XyKY36MNG8UtGp8Dm1PVh/LrVJaUfhiyz fp+g== 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=xMrzQR+hyu5EXuGwNLs8nXmODpv9VFpRyvX7+WB10Ns=; b=VZvqTSYbP8+yiG5U1c+amF8729o1Xa7JeikwETGgRu9YaS+U6/5k9IPzL9UNiq+hlD afgkh8WJICvPXg0c7kqPb6oh2RpxLriRtuBSyOqCdO9n55SMF8jfxpRItNyqXjFzAa+n ibhQGXgBF6okepWhyoWgHn2G/RZHZDVpvFpDyKoC8fUsCxVGRhbrHPk+ojtrNKJ67DUo Th2VPddUb4tyvV0RHQAhmIRwhlRrYaYuS/PhcM3/fTjlAUFiBbjC9vpFe1MOQMYlyQIu 39Lzm+chcxzQ6Q0ZCDvLbOAqK4AVaaAcFF6OnwJXqZJsm8chLm5NbMN+lqu/XJtHrU/o 1Tyw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id la1si7261039ejb.235.2020.05.18.08.56.01; Mon, 18 May 2020 08:56:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728260AbgERPyp (ORCPT + 99 others); Mon, 18 May 2020 11:54:45 -0400 Received: from foss.arm.com ([217.140.110.172]:43270 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727007AbgERPyp (ORCPT ); Mon, 18 May 2020 11:54:45 -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 36DDF106F; Mon, 18 May 2020 08:54:44 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 71C243F52E; Mon, 18 May 2020 08:54:42 -0700 (PDT) Date: Mon, 18 May 2020 16:54:35 +0100 From: Lorenzo Pieralisi To: Bjorn Helgaas Cc: Vidya Sagar , jingoohan1@gmail.com, gustavo.pimentel@synopsys.com, Andrew Murray , bhelgaas@google.com, thierry.reding@gmail.com, jonathanh@nvidia.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com, Alan Mikhak Subject: Re: [PATCH] PCI: dwc: Warn only for non-prefetchable memory resource size >4GB Message-ID: <20200518155435.GA2299@e121166-lin.cambridge.arm.com> References: <20200513190855.23318-1-vidyas@nvidia.com> <20200513223508.GA352288@bjorn-Precision-5520> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200513223508.GA352288@bjorn-Precision-5520> 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 Wed, May 13, 2020 at 05:35:08PM -0500, Bjorn Helgaas wrote: > [+cc Alan; please cc authors of relevant commits, > updated Andrew's email address] > > On Thu, May 14, 2020 at 12:38:55AM +0530, Vidya Sagar wrote: > > commit 9e73fa02aa009 ("PCI: dwc: Warn if MEM resource size exceeds max for > > 32-bits") enables warning for MEM resources of size >4GB but prefetchable > > memory resources also come under this category where sizes can go beyond > > 4GB. Avoid logging a warning for prefetchable memory resources. > > > > Signed-off-by: Vidya Sagar > > --- > > drivers/pci/controller/dwc/pcie-designware-host.c | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c > > index 42fbfe2a1b8f..a29396529ea4 100644 > > --- a/drivers/pci/controller/dwc/pcie-designware-host.c > > +++ b/drivers/pci/controller/dwc/pcie-designware-host.c > > @@ -366,7 +366,8 @@ int dw_pcie_host_init(struct pcie_port *pp) > > pp->mem = win->res; > > pp->mem->name = "MEM"; > > mem_size = resource_size(pp->mem); > > - if (upper_32_bits(mem_size)) > > + if (upper_32_bits(mem_size) && > > + !(win->res->flags & IORESOURCE_PREFETCH)) > > dev_warn(dev, "MEM resource size exceeds max for 32 bits\n"); > > pp->mem_size = mem_size; > > pp->mem_bus_addr = pp->mem->start - win->offset; That warning was added for a reason - why should not we log legitimate warnings ? AFAIU having resources larger than 4GB can lead to undefined behaviour given the current ATU programming API. Alan ? I want to understand what's the best course of action before merging these patches. Lorenzo