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=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 06B8AC433F5 for ; Mon, 6 Sep 2021 19:53:54 +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 BD58D61050 for ; Mon, 6 Sep 2021 19:53:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BD58D61050 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=w2lEtdoT5Cam5eqNQOYTUDXcwPT4sGYX8wB0egfGH4g=; b=E7KXzLOlcvZSGq NideMelwXcXYJdSq3hrw9ENHzse8bxXpDVqQnxjy6aX38AEfbWcisjE3XiaP8qElu1eXphH5NNPbz gO7hrvX0xjtVG1GNHIgIDZQjvNwk5tvgfa6LVqqQgLvcN8XmjGRD9L8fM8muBLSqk3WXVkJiZhvo/ 8a6OcUZcTWb18rdzVt1GdKwsSBZgZ9/gALbUyDxPMkoC4X6qyHUinvYLHxIlzhY3xoBmAE7GbcABf iKuma8ZqBXQu+bm69Fi+qHbqzYEAF770Yauhd/3mbB91fF0IY5MQk8w/qN5STex6IKnKh68OKK3QE YYNqzzWjANZlDgn9thxQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mNKem-001oru-9P; Mon, 06 Sep 2021 19:51:52 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mNKeh-001orY-Qf for linux-arm-kernel@lists.infradead.org; Mon, 06 Sep 2021 19:51:49 +0000 Received: by mail-ej1-x633.google.com with SMTP id t19so15301607ejr.8 for ; Mon, 06 Sep 2021 12:51:45 -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=pYOIpfoLo1TtPOzly7mCruZDinHXZD4jqzh3rEOq7zU=; b=s3VQGvmRtztPI/5nkbWDZhH4pFe2TIABlDp9Z4ocjsCKX4PDE5lS0Xfw2D3tPHfE0K IRdlSlSYBRq3ksBcjj4FlA1WQgfp9k0TsJ/VPYDPK/9CrKI8Oivb9TrxVV9lhjqXRARK Z6UNm59nnYqVrlDeEcWV46FrlSEhEorZJIOZ9CrAhRqECaTzeMAxSwfxopz83GR7C4jE 87yuKzScHDkbr42z4doa7OOaiRxeCFV16WoK5GLhM2yFM8wErVYhGp8IbbS64WuSE7Gj TB/pyQIvrHjVn2Q2+znoBB1ZKsSKEO1B/Ehwkwwafs9nQpWMkEBS8WD24g0+k+z6BTtj 9SWQ== 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=pYOIpfoLo1TtPOzly7mCruZDinHXZD4jqzh3rEOq7zU=; b=sx8q6dNaFJM8pLbmTKW8y95ZR0jhJtOtRX/3+LqPuJrmRsDSTeywdnR5V3LEwDU0wb qrirM7Kgmy/hvUfjtKpYVNa8n6elHRrN4nJZ5jTv3G7ydhA7nMICQCfFK+9G3EHl6VTZ CugLNIUl5sQd35PPfHTXEADq5tWwaVx1luheVCPvOx95rfFuOTNe79l/JxvRkStMPCRV 4dWVkhGIhOdE+NpCOpmoeMQqRIBhsnuZgk589s+25pG2AiN6j30H1hzU8O1WCAi0UMUw ygOG2gZ/ollqnk3RPPAg0Gbwjz0IrvaQtVHYlSJNQY++FHVNhJett+zMG/5FdE74T0t0 fiFw== X-Gm-Message-State: AOAM53180fsswF4MaEHAFCH/aK/4ng6wm1CLFc64h7OEjkZxeBOd+k/s Gat1za7tS9SkmkWvb+oiZCcvAVt0hPnoBgE94ljuOg== X-Google-Smtp-Source: ABdhPJzNmHxJtz1P9ezhqHwwF8nhs91bYyqdz6r0gtgvcPAfCo1su2ltyZrM7CQ2UDeayDx0mJOExFIsSv7h5nCpJjQ= X-Received: by 2002:a17:906:d04f:: with SMTP id bo15mr15064287ejb.309.1630957904502; Mon, 06 Sep 2021 12:51:44 -0700 (PDT) MIME-Version: 1.0 References: <20210805080724.480-1-shameerali.kolothum.thodi@huawei.com> <20210805080724.480-3-shameerali.kolothum.thodi@huawei.com> <20210805160319.GB23085@lpieralisi> <5d9bebdf-6eb5-49a0-2e8f-490df2d6754d@arm.com> In-Reply-To: <5d9bebdf-6eb5-49a0-2e8f-490df2d6754d@arm.com> From: Jon Nettleton Date: Mon, 6 Sep 2021 21:51:07 +0200 Message-ID: Subject: Re: [PATCH v7 2/9] ACPI/IORT: Add support for RMR node parsing To: Robin Murphy Cc: Lorenzo Pieralisi , Shameer Kolothum , Laurentiu Tudor , linux-arm-kernel , ACPI Devel Maling List , Linux IOMMU , Linuxarm , Joerg Roedel , Will Deacon , wanghuiqiang , 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-20210906_125147_956083_91A5315A X-CRM114-Status: GOOD ( 33.16 ) 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 Mon, Sep 6, 2021 at 7:44 PM Robin Murphy wrote: > > On 2021-08-05 17:03, Lorenzo Pieralisi wrote: > > On Thu, Aug 05, 2021 at 09:07:17AM +0100, Shameer Kolothum wrote: > > > > [...] > > > >> +static void __init iort_node_get_rmr_info(struct acpi_iort_node *iort_node) > >> +{ > >> + struct acpi_iort_node *smmu; > >> + struct acpi_iort_rmr *rmr; > >> + struct acpi_iort_rmr_desc *rmr_desc; > >> + u32 map_count = iort_node->mapping_count; > >> + u32 sid; > >> + int i; > >> + > >> + if (!iort_node->mapping_offset || map_count != 1) { > >> + pr_err(FW_BUG "Invalid ID mapping, skipping RMR node %p\n", > >> + iort_node); > >> + return; > >> + } > >> + > >> + /* Retrieve associated smmu and stream id */ > >> + smmu = iort_node_get_id(iort_node, &sid, 0); > >> + if (!smmu) { > >> + pr_err(FW_BUG "Invalid SMMU reference, skipping RMR node %p\n", > >> + iort_node); > >> + return; > >> + } > >> + > >> + /* Retrieve RMR data */ > >> + rmr = (struct acpi_iort_rmr *)iort_node->node_data; > >> + if (!rmr->rmr_offset || !rmr->rmr_count) { > >> + pr_err(FW_BUG "Invalid RMR descriptor array, skipping RMR node %p\n", > >> + iort_node); > >> + return; > >> + } > >> + > >> + rmr_desc = ACPI_ADD_PTR(struct acpi_iort_rmr_desc, iort_node, > >> + rmr->rmr_offset); > >> + > >> + iort_rmr_desc_check_overlap(rmr_desc, rmr->rmr_count); > >> + > >> + for (i = 0; i < rmr->rmr_count; i++, rmr_desc++) { > >> + struct iommu_resv_region *region; > >> + enum iommu_resv_type type; > >> + int prot = IOMMU_READ | IOMMU_WRITE; > >> + u64 addr = rmr_desc->base_address, size = rmr_desc->length; > >> + > >> + if (!IS_ALIGNED(addr, SZ_64K) || !IS_ALIGNED(size, SZ_64K)) { > >> + /* PAGE align base addr and size */ > >> + addr &= PAGE_MASK; > >> + size = PAGE_ALIGN(size + offset_in_page(rmr_desc->base_address)); > >> + > >> + pr_err(FW_BUG "RMR descriptor[0x%llx - 0x%llx] not aligned to 64K, continue with [0x%llx - 0x%llx]\n", > >> + rmr_desc->base_address, > >> + rmr_desc->base_address + rmr_desc->length - 1, > >> + addr, addr + size - 1); > >> + } > >> + if (rmr->flags & IOMMU_RMR_REMAP_PERMITTED) { > >> + type = IOMMU_RESV_DIRECT_RELAXABLE; > >> + /* > >> + * Set IOMMU_CACHE as IOMMU_RESV_DIRECT_RELAXABLE is > >> + * normally used for allocated system memory that is > >> + * then used for device specific reserved regions. > >> + */ > >> + prot |= IOMMU_CACHE; > >> + } else { > >> + type = IOMMU_RESV_DIRECT; > >> + /* > >> + * Set IOMMU_MMIO as IOMMU_RESV_DIRECT is normally used > >> + * for device memory like MSI doorbell. > >> + */ > >> + prot |= IOMMU_MMIO; > >> + } > > > > On the prot value assignment based on the remapping flag, I'd like to > > hear Robin/Joerg's opinion, I'd avoid being in a situation where > > "normally" this would work but then we have to quirk it. > > > > Is this a valid assumption _always_ ? > > No. Certainly applying IOMMU_CACHE without reference to the device's > _CCA attribute or how CPUs may be accessing a shared buffer could lead > to a loss of coherency. At worst, applying IOMMU_MMIO to a > device-private buffer *could* cause the device to lose coherency with > itself if the memory underlying the RMR may have allocated into system > caches. Note that the expected use for non-remappable RMRs is the device > holding some sort of long-lived private data in system RAM - the MSI > doorbell trick is far more of a niche hack really. > > At the very least I think we need to refer to the device's memory access > properties here. > > Jon, Laurentiu - how do RMRs correspond to the EFI memory map on your > firmware? I'm starting to think that as long as the underlying memory is > described appropriately there then we should be able to infer correct > attributes from the EFI memory type and flags. The devices are all cache coherent and marked as _CCA, 1. The Memory regions are in the virt table as ARM_MEMORY_REGION_ATTRIBUTE_DEVICE. The current chicken and egg problem we have is that during the fsl-mc-bus initialization we call error = acpi_dma_configure_id(&pdev->dev, DEV_DMA_COHERENT, &mc_stream_id); which gets deferred because the SMMU has not been initialized yet. Then we initialize the RMR tables but there is no device reference there to be able to query device properties, only the stream id. After the IORT tables are parsed and the SMMU is setup, on the second device probe we associate everything based on the stream id and the fsl-mc-bus device is able to claim its 1-1 DMA mappings. cat /sys/kernel/iommu_groups/0/reserved_regions 0x0000000001000000 0x0000000010ffffff direct-relaxable 0x0000000008000000 0x00000000080fffff msi 0x000000080c000000 0x000000081bffffff direct-relaxable 0x0000001c00000000 0x0000001c001fffff direct-relaxable 0x0000002080000000 0x000000209fffffff direct-relaxable -Jon > > Robin. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel