Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp5958487rwi; Tue, 18 Oct 2022 06:29:12 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7shM+sJ4+1fkkKzIWtXl4TLbm+UQfESTYXZMky5cIlQIbppk86rN1404DurXtOVtMGc2vc X-Received: by 2002:a17:902:f708:b0:178:9b70:310b with SMTP id h8-20020a170902f70800b001789b70310bmr2957671plo.65.1666099751877; Tue, 18 Oct 2022 06:29:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666099751; cv=none; d=google.com; s=arc-20160816; b=gKTXrMS8aQxAlkdMrFmzxbyXrWWp8Sty3Y0eTGxLvdWDriiW4mVAuXx8Nxnmw5HoiP hrXdf/5MsLbHbw8CoLHz+5cLEUk/ILDczKpkoP9iW9TyXguH+o5GUTfLbzWHV/YT+gTZ L3LX+9WGheejwVMxyN5tUrYBVuv2Wnc7EkYP0VfxHGTOBkwa/qte4PJddgbAK03uJB2P 4Vubr8xyn5c+3OGLY7A47IQ3vDG7WpeLYWobMp5Fkrs+nUJ3JSF1ILYCpR0BlQ1gEQbW qvnA7AEiQZQJEcfqo0MjVvCcYQDfzoYiAZknk1BuRv8q3vCaS6nbaPQiBMQrVsEgr6N/ EX4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:to:subject :cc; bh=bu7U4UYa7C7nPmiMBKQ3QxTAcnO6+gRP7v1LxnjHU40=; b=edtEPZ4nP+JJcO9z3UGxzn+T+LUuUtAllbch+C2YuRbsQg/nRvEwb36iCPadvpQxwV eVtpsIM9jpc2xB23iuEkOLy8g3JFIQGVMyRiY+YYGCsQNk0HBDFR/S7q4eYQwhKUzMLF tLU5guNBIEVqfdo7Jywv5BGGa8rmGtjJGH9StOUVGGi4gm1z9T10gSMBLM9JFxJTBoX7 bTUYsgk1Eqk+s2umK86P6QjekqUXGHfZ5ToDrlKolmuM576ZyhHXKE9yPQsPUsQ/BB+a ew6Asom94abOXrXMKjV2FUwYVwadJPnTPVX7OB6wowgqS5/Tmo2kkzKXeZOeKrZQQNIQ CdPQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t22-20020a634616000000b00434ba40afd5si15973451pga.873.2022.10.18.06.28.56; Tue, 18 Oct 2022 06:29:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229961AbiJRMcu (ORCPT + 99 others); Tue, 18 Oct 2022 08:32:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60624 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229718AbiJRMcs (ORCPT ); Tue, 18 Oct 2022 08:32:48 -0400 Received: from szxga08-in.huawei.com (szxga08-in.huawei.com [45.249.212.255]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 06292C2CA8; Tue, 18 Oct 2022 05:32:43 -0700 (PDT) Received: from canpemm500009.china.huawei.com (unknown [172.30.72.53]) by szxga08-in.huawei.com (SkyGuard) with ESMTP id 4MsCnB6JmGz1P71d; Tue, 18 Oct 2022 20:27:58 +0800 (CST) Received: from [10.67.102.169] (10.67.102.169) by canpemm500009.china.huawei.com (7.192.105.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 18 Oct 2022 20:32:41 +0800 CC: , Jianmin Lv , , , , , , , , , , liulongfang Subject: Re: [PATCH V5 1/2] ACPI / scan: Support multiple dma windows with different offsets To: Robin Murphy , "Rafael J. Wysocki" References: <20220911090635.5559-1-lvjianmin@loongson.cn> <20220911090635.5559-2-lvjianmin@loongson.cn> <8e9df8ea-06f0-3989-2563-d5dc6b09a062@huawei.com> From: Yicong Yang Message-ID: <7904cd2e-caf5-0073-9889-306ab524d802@huawei.com> Date: Tue, 18 Oct 2022 20:32:40 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.102.169] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To canpemm500009.china.huawei.com (7.192.105.203) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/10/18 20:00, Robin Murphy wrote: > On 2022-10-18 11:08, Rafael J. Wysocki wrote: >> On Tue, Oct 18, 2022 at 11:33 AM Yicong Yang wrote: >>> >>> On 2022/9/11 17:06, Jianmin Lv wrote: >>>> In DT systems configurations, of_dma_get_range() returns struct >>>> bus_dma_region DMA regions; they are used to set-up devices >>>> DMA windows with different offset available for translation between DMA >>>> address and CPU address. >>>> >>>> In ACPI systems configuration, acpi_dma_get_range() does not return >>>> DMA regions yet and that precludes setting up the dev->dma_range_map >>>> pointer and therefore DMA regions with multiple offsets. >>>> >>>> Update acpi_dma_get_range() to return struct bus_dma_region >>>> DMA regions like of_dma_get_range() does. >>>> >>>> After updating acpi_dma_get_range(), acpi_arch_dma_setup() is changed for >>>> ARM64, where the original dma_addr and size are removed as these >>>> arguments are now redundant, and pass 0 and U64_MAX for dma_base >>>> and size of arch_setup_dma_ops; this is a simplification consistent >>>> with what other ACPI architectures also pass to iommu_setup_dma_ops(). >>>> >>> >>> Hi, >>> >>> With this patch we met problem as well. The DMA coherent mask is not set correctly >>> for a ehci usb controller and lead to the below calltrace: >>> >>> [   16.699259] ------------[ cut here ]------------ >>> [   16.703855] WARNING: CPU: 0 PID: 853 at kernel/dma/mapping.c:499 dma_alloc_attrs+0xc0/0xf0 >>> [   16.712082] Modules linked in: >>> [   16.715124] CPU: 0 PID: 853 Comm: kworker/0:3 Not tainted 6.1.0-rc1-pipe-deadlock+ #5 >>> [   16.722916] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V5.B211.01 11/10/2021 >>> [   16.731745] Workqueue: events work_for_cpu_fn >>> [   16.736083] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) >>> [   16.743013] pc : dma_alloc_attrs+0xc0/0xf0 >>> [   16.747091] lr : dma_pool_alloc+0x11c/0x200 >>> [   16.751255] sp : ffff80001e46bb50 >>> [   16.754554] x29: ffff80001e46bb50 x28: 0000000000000000 x27: 0000000000000000 >>> [   16.761657] x26: ffff80000b33ce18 x25: ffff800009cc6c48 x24: 0000000000000000 >>> [   16.768759] x23: ffff00208c830918 x22: 0000000000001000 x21: 0000000000000cc0 >>> [   16.775861] x20: ffff00208ae82080 x19: ffff0020865c40d0 x18: 0000000000000030 >>> [   16.782964] x17: 626d756e20737562 x16: 2064656e67697373 x15: ffff00208ae82640 >>> [   16.790066] x14: 0000000000000000 x13: 646e756f72616b72 x12: 6f77204348207379 >>> [   16.797167] x11: 73706f6e79532067 x10: ffff205f43980000 x9 : ffff80000830b3ac >>> [   16.804269] x8 : ffff0020861b1b00 x7 : 0000000000000000 x6 : 0000000000000000 >>> [   16.811371] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000cc0 >>> [   16.818472] x2 : ffff00208c830918 x1 : 0000000000001000 x0 : 0000000000000000 >>> [   16.825574] Call trace: >>> [   16.828009]  dma_alloc_attrs+0xc0/0xf0 >>> [   16.831741]  dma_pool_alloc+0x11c/0x200 >>> [   16.835559]  ehci_qh_alloc+0x60/0x12c >>> [   16.839207]  ehci_setup+0x18c/0x40c >>> [   16.842680]  ehci_pci_setup+0xb8/0x680 >>> [   16.846412]  usb_add_hcd+0x310/0x5c0 >>> [   16.849973]  usb_hcd_pci_probe+0x254/0x36c >>> [   16.854051]  ehci_pci_probe+0x40/0x60 >>> [   16.857698]  local_pci_probe+0x48/0xb4 >>> [   16.861431]  work_for_cpu_fn+0x24/0x40 >>> [   16.865163]  process_one_work+0x1e0/0x450 >>> [   16.869155]  worker_thread+0x2cc/0x44c >>> [   16.872886]  kthread+0x114/0x120 >>> [   16.876099]  ret_from_fork+0x10/0x20 >>> [   16.879657] ---[ end trace 0000000000000000 ]--- >>> >>> After reverting this patch the problem resolved. Tested on the latest 6.1-rc1. >> >> OK, I'll queue up a revert of this and one more commit depending on it. > > FWIW it looks like the fix should be as simple as below. > Looks like it's the case. The change works on my platform, now the ehci probed successfully again with no calltrace: Tested-by: Yicong Yang > Robin. > > ----->8----- > diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c > index 558664d169fc..b6962bff1eae 100644 > --- a/drivers/acpi/scan.c > +++ b/drivers/acpi/scan.c > @@ -1509,6 +1509,7 @@ int acpi_dma_get_range(struct device *dev, const struct bus_dma_region **map) >              goto out; >          } > > +        *map = r; >          list_for_each_entry(rentry, &list, node) { >              if (rentry->res->start >= rentry->res->end) { >                  kfree(r); > @@ -1523,8 +1524,6 @@ int acpi_dma_get_range(struct device *dev, const struct bus_dma_region **map) >              r->offset = rentry->offset; >              r++; >          } > - > -        *map = r; >      } >   out: >      acpi_dev_free_resource_list(&list); > > .