From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 846AAC432BE for ; Tue, 31 Aug 2021 05:10:01 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 41B816103D for ; Tue, 31 Aug 2021 05:10:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 41B816103D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=solid-run.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=t/qa6dEIDTmMZtU/sC0i/jScYlWqDxKIC/1DBaEil9c=; b=sehEopxMvevqRy ZmmO+sPOiEbv5/gDLYp/4djssifzGlLgX8pZBJbpamXa7o/h+2mIzUV1T2a/MH4UoVNYh/eIz3Efx QEuDgCzZHGNbJuKU2pMjZX1rF90zzDZQKh0RuJ1dRLomxETCJJINpn6NxlkaUzkEjabEs7EGbIGv0 OfSuwDUQTbAScjcBQcD/Hcryk3i8W6Bfa4uXyAbuK2j/tvIf8kuU3uZZtrEHCsDDqaoyS0LkQkXst GyE7rcN+KnyuCNVMCNUoGDc4Ue1WuahiU/Ehjq1MlBhfqF99udakFNn3MGw0JP0CnWxROk7BhSgSV Ka6enm0x+fewOmd1ztZg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mKvzs-001LKC-Fo; Tue, 31 Aug 2021 05:07:44 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mKvzm-001LJm-IM for linux-arm-kernel@lists.infradead.org; Tue, 31 Aug 2021 05:07:42 +0000 Received: by mail-ed1-x535.google.com with SMTP id g21so24919793edw.4 for ; Mon, 30 Aug 2021 22:07:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=solid-run-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+9JLMUEGuTSyUphLOiuK/o3WrAb7TWs20Kwls76RPEk=; b=X0wZCLCMDC9sOHDwi7WuzV8/HIEOdVWVnVcQzbv+QeObhsCAvWlPLJ+q1K4decobT2 Rjz7HVerG6qQBUs316Ns6qzYJ7J+gb0AgJWwZFZlf8GkGzI8MelZQO5E83uTeiXBsNS+ q96xFs8glcHHP7ug/irAHZ1TtvDKvpD4AqJPHpueP047PMOiXfDrOnXwEQEE3jAzfsoa SU13O9Po/RysClarcjxeCkvfTJ1NPvfYXb6ahOQb41hMuA7HPhcdmwKTpC/Bqb1eCje6 XtwcfbKbrJEoOit6kq/cZU4HYiGbNa3Uc2gI1wQDztKzQ2g1F2RytBFxm+S3LflKARBL UCrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+9JLMUEGuTSyUphLOiuK/o3WrAb7TWs20Kwls76RPEk=; b=mFHq7AyaYXtFE8boQZSe84lEDcMyGcoMvGEzfFoKp6R+VcromjdvbwLwPSFsW77V8H fpGw31xDAuHgDTPSXHWV009y81vMCWKMVpz5brQV74flGIM2NC5NF5BQAnVq/5hfRAou Xit9y84fjLJbudavgUxbRIvMMCCkx8JXvA18lByBqljuQ5PLkuuqMXHQc6rfjnDYelTm 00wcrIE/1HEHgyoFOGx282zvYflgwLOlV6hcnHZTC6JFDW4rTJqTosE9DveV+zFTApwP t6oVC7+ktYcw72Usqj0Dm6DhGSyvz+CuhFUlVmKDdEGFNT0YMKFgMZ0AD49SSeJEQ2fV ceSw== X-Gm-Message-State: AOAM531oTgvlXGxT156TUnujWr6aq32MzZ26u5kVjf6y2t62oTaVc97g Ud81cGcnp3eSf/ofNIpX3/dIA986f2qw1reJlgsrJw== X-Google-Smtp-Source: ABdhPJw3bs9klmA4ZwzYsj0W52rj0T5yFqeP2kB+dZoyUd8oOW4bpTE8uDnH+x9cAw6FSmg6O3ZRvWW3aUfpYw8S8OI= X-Received: by 2002:aa7:dd12:: with SMTP id i18mr27577652edv.368.1630386455037; Mon, 30 Aug 2021 22:07:35 -0700 (PDT) MIME-Version: 1.0 References: <20210805080724.480-1-shameerali.kolothum.thodi@huawei.com> <8df7fc81b00142b68126efd3c700a579@huawei.com> In-Reply-To: From: Jon Nettleton Date: Tue, 31 Aug 2021 07:06:58 +0200 Message-ID: Subject: Re: [PATCH v7 0/9] ACPI/IORT: Support for IORT RMR node To: Ard Biesheuvel Cc: Shameerali Kolothum Thodi , Linux ARM , ACPI Devel Maling List , Linux IOMMU , Linuxarm , Lorenzo Pieralisi , Joerg Roedel , Robin Murphy , Will Deacon , wanghuiqiang , "Guohanjun (Hanjun Guo)" , Steven Price , Sami Mujawar , Eric Auger , yangyicong X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210830_220738_699341_33E1524D X-CRM114-Status: GOOD ( 47.09 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Aug 5, 2021 at 4:09 PM Ard Biesheuvel wrote: > > On Thu, 5 Aug 2021 at 15:35, Shameerali Kolothum Thodi > wrote: > > > > > > > > > -----Original Message----- > > > From: Ard Biesheuvel [mailto:ardb@kernel.org] > > > Sent: 05 August 2021 14:23 > > > To: Shameerali Kolothum Thodi > > > Cc: Linux ARM ; ACPI Devel Maling List > > > ; Linux IOMMU > > > ; Linuxarm ; > > > Lorenzo Pieralisi ; Joerg Roedel > > > ; Robin Murphy ; Will Deacon > > > ; wanghuiqiang ; Guohanjun > > > (Hanjun Guo) ; Steven Price > > > ; Sami Mujawar ; Jon > > > Nettleton ; Eric Auger ; > > > yangyicong > > > Subject: Re: [PATCH v7 0/9] ACPI/IORT: Support for IORT RMR node > > > > > > On Thu, 5 Aug 2021 at 10:10, Shameer Kolothum > > > wrote: > > > > > > > > Hi, > > > > > > > > The series adds support to IORT RMR nodes specified in IORT > > > > Revision E.b -ARM DEN 0049E[0]. RMR nodes are used to describe > > > > memory ranges that are used by endpoints and require a unity > > > > mapping in SMMU. > > > > > > > > We have faced issues with 3408iMR RAID controller cards which > > > > fail to boot when SMMU is enabled. This is because these > > > > controllers make use of host memory for various caching related > > > > purposes and when SMMU is enabled the iMR firmware fails to > > > > access these memory regions as there is no mapping for them. > > > > IORT RMR provides a way for UEFI to describe and report these > > > > memory regions so that the kernel can make a unity mapping for > > > > these in SMMU. > > > > > > > > > > Does this mean we are ignoring the RMR memory ranges, and exposing the > > > entire physical address space to devices using the stream IDs in > > > question? > > > > Nope. RMR node is used to describe the memory ranges used by end points > > behind SMMU. And this information is used to create 1 : 1 mappings for those > > ranges in SMMU. Anything outside those ranges will result in translation > > fault(if there are no other dynamic DMA mappings). > > > > Excellent! It was not obvious to me from looking at the patches, so I > had to ask. > > Thanks, > Ard. > > > > > > > > > > Change History: > > > > > > > > v6 --> v7 > > > > > > > > The only change from v6 is the fix pointed out by Steve to > > > > the SMMUv2 SMR bypass install in patch #8. > > > > > > > > Thanks to the Tested-by tags by Laurentiu with SMMUv2 and > > > > Hanjun/Huiqiang with SMMUv3 for v6. I haven't added the tags > > > > yet as the series still needs more review[1]. > > > > > > > > Feedback and tests on this series is very much appreciated. > > > > > > > > v5 --> v6 > > > > - Addressed comments from Robin & Lorenzo. > > > > : Moved iort_parse_rmr() to acpi_iort_init() from > > > > iort_init_platform_devices(). > > > > : Removed use of struct iort_rmr_entry during the initial > > > > parse. Using struct iommu_resv_region instead. > > > > : Report RMR address alignment and overlap errors, but continue. > > > > : Reworked arm_smmu_init_bypass_stes() (patch # 6). > > > > - Updated SMMUv2 bypass SMR code. Thanks to Jon N (patch #8). > > > > - Set IOMMU protection flags(IOMMU_CACHE, IOMMU_MMIO) based > > > > on Type of RMR region. Suggested by Jon N. > > > > > > > > Thanks, > > > > Shameer > > > > [0] https://developer.arm.com/documentation/den0049/latest/ > > > > [1] > > > https://lore.kernel.org/linux-acpi/20210716083442.1708-1-shameerali.koloth > > > um.thodi@huawei.com/T/#m043c95b869973a834b2fd57f3e1ed0325c84f3b7 > > > > ------ > > > > v4 --> v5 > > > > -Added a fw_data union to struct iommu_resv_region and removed > > > > struct iommu_rmr (Based on comments from Joerg/Robin). > > > > -Added iommu_put_rmrs() to release mem. > > > > -Thanks to Steve for verifying on SMMUv2, but not added the Tested-by > > > > yet because of the above changes. > > > > > > > > v3 -->v4 > > > > -Included the SMMUv2 SMR bypass install changes suggested by > > > > Steve(patch #7) > > > > -As per Robin's comments, RMR reserve implementation is now > > > > more generic (patch #8) and dropped v3 patches 8 and 10. > > > > -Rebase to 5.13-rc1 > > > > > > > > RFC v2 --> v3 > > > > -Dropped RFC tag as the ACPICA header changes are now ready to be > > > > part of 5.13[0]. But this series still has a dependency on that patch. > > > > -Added IORT E.b related changes(node flags, _DSM function 5 checks for > > > > PCIe). > > > > -Changed RMR to stream id mapping from M:N to M:1 as per the spec and > > > > discussion here[1]. > > > > -Last two patches add support for SMMUv2(Thanks to Jon Nettleton!) > > > > ------ > > > > > > > > Jon Nettleton (1): > > > > iommu/arm-smmu: Get associated RMR info and install bypass SMR > > > > > > > > Shameer Kolothum (8): > > > > iommu: Introduce a union to struct iommu_resv_region > > > > ACPI/IORT: Add support for RMR node parsing > > > > iommu/dma: Introduce generic helper to retrieve RMR info > > > > ACPI/IORT: Add a helper to retrieve RMR memory regions > > > > iommu/arm-smmu-v3: Introduce strtab init helper > > > > iommu/arm-smmu-v3: Refactor arm_smmu_init_bypass_stes() to force > > > > bypass > > > > iommu/arm-smmu-v3: Get associated RMR info and install bypass STE > > > > iommu/dma: Reserve any RMR regions associated with a dev > > > > > > > > drivers/acpi/arm64/iort.c | 172 > > > +++++++++++++++++++- > > > > drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 76 +++++++-- > > > > drivers/iommu/arm/arm-smmu/arm-smmu.c | 48 ++++++ > > > > drivers/iommu/dma-iommu.c | 89 +++++++++- > > > > include/linux/acpi_iort.h | 7 + > > > > include/linux/dma-iommu.h | 13 ++ > > > > include/linux/iommu.h | 11 ++ > > > > 7 files changed, 393 insertions(+), 23 deletions(-) > > > > > > > > -- > > > > 2.17.1 > > > > > > > > > > > > _______________________________________________ > > > > linux-arm-kernel mailing list > > > > linux-arm-kernel@lists.infradead.org > > > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel Ping, Can we get some movement on this patchset? The standard was was ratified over a year ago, and there is real world hardware that is using or needs this functionality. Thanks, -Jon _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel