LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com> To: Rajat Jain <rajatja@google.com> Cc: joro@8bytes.org, will@kernel.org, iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com, baolu.lu@linux.intel.com, john.garry@huawei.com, dianders@chromium.org, chenxiang66@hisilicon.com Subject: Re: [PATCH v3 24/25] iommu/dma: Factor out flush queue init Date: Mon, 9 Aug 2021 20:59:35 +0100 [thread overview] Message-ID: <00baf83a-5eb3-4d72-309c-5adfd3242c07@arm.com> (raw) In-Reply-To: <CACK8Z6HSM678q=BZ3FY7spN2S3ZkhdJ3ecnMCbKWrqB5dNWaMA@mail.gmail.com> On 2021-08-09 20:05, Rajat Jain wrote: > On Wed, Aug 4, 2021 at 10:16 AM Robin Murphy <robin.murphy@arm.com> wrote: >> >> Factor out flush queue setup from the initial domain init so that we >> can potentially trigger it from sysfs later on in a domain's lifetime. >> >> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com> >> Reviewed-by: John Garry <john.garry@huawei.com> >> Signed-off-by: Robin Murphy <robin.murphy@arm.com> >> --- >> drivers/iommu/dma-iommu.c | 30 ++++++++++++++++++++---------- >> include/linux/dma-iommu.h | 9 ++++++--- >> 2 files changed, 26 insertions(+), 13 deletions(-) >> >> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c >> index 2e19505dddf9..f51b8dc99ac6 100644 >> --- a/drivers/iommu/dma-iommu.c >> +++ b/drivers/iommu/dma-iommu.c >> @@ -310,6 +310,25 @@ static bool dev_is_untrusted(struct device *dev) >> return dev_is_pci(dev) && to_pci_dev(dev)->untrusted; >> } >> >> +int iommu_dma_init_fq(struct iommu_domain *domain) >> +{ >> + struct iommu_dma_cookie *cookie = domain->iova_cookie; >> + >> + if (domain->type != IOMMU_DOMAIN_DMA_FQ) >> + return -EINVAL; >> + if (cookie->fq_domain) >> + return 0; >> + >> + if (init_iova_flush_queue(&cookie->iovad, iommu_dma_flush_iotlb_all, >> + iommu_dma_entry_dtor)) { >> + pr_warn("iova flush queue initialization failed\n"); >> + domain->type = IOMMU_DOMAIN_DMA; >> + return -ENODEV; >> + } >> + cookie->fq_domain = domain; >> + return 0; >> +} >> + >> /** >> * iommu_dma_init_domain - Initialise a DMA mapping domain >> * @domain: IOMMU domain previously prepared by iommu_get_dma_cookie() >> @@ -362,16 +381,7 @@ static int iommu_dma_init_domain(struct iommu_domain *domain, dma_addr_t base, >> } >> >> init_iova_domain(iovad, 1UL << order, base_pfn); >> - >> - if (domain->type == IOMMU_DOMAIN_DMA_FQ && !cookie->fq_domain) { >> - if (init_iova_flush_queue(iovad, iommu_dma_flush_iotlb_all, >> - iommu_dma_entry_dtor)) { >> - pr_warn("iova flush queue initialization failed\n"); >> - domain->type = IOMMU_DOMAIN_DMA; >> - } else { >> - cookie->fq_domain = domain; >> - } >> - } >> + iommu_dma_init_fq(domain); >> >> return iova_reserve_iommu_regions(dev, domain); >> } >> diff --git a/include/linux/dma-iommu.h b/include/linux/dma-iommu.h >> index 758ca4694257..81ab647f1618 100644 >> --- a/include/linux/dma-iommu.h >> +++ b/include/linux/dma-iommu.h >> @@ -20,6 +20,7 @@ void iommu_put_dma_cookie(struct iommu_domain *domain); >> >> /* Setup call for arch DMA mapping code */ >> void iommu_setup_dma_ops(struct device *dev, u64 dma_base, u64 dma_limit); >> +int iommu_dma_init_fq(struct iommu_domain *domain); >> >> /* The DMA API isn't _quite_ the whole story, though... */ >> /* >> @@ -37,9 +38,6 @@ void iommu_dma_compose_msi_msg(struct msi_desc *desc, >> >> void iommu_dma_get_resv_regions(struct device *dev, struct list_head *list); >> >> -void iommu_dma_free_cpu_cached_iovas(unsigned int cpu, >> - struct iommu_domain *domain); >> - > > This looks like an unrelated code cleanup. Should this be a separate patch? Ha, busted! Much of this was done in the "stream of consciousness" style where I made a big sprawling mess then split it up into patches and branches afterwards. TBH it was already feeling pretty tenuous having a separate patch just to move this one function, and it only gets more so with the simplification Will pointed out earlier. I think I'll squash iommu_dma_init_fq() into the next patch then do a thorough header sweep, since I've now spotted some things in iova.h which could probably go as well. Thanks for the poke! Robin. > > Thanks, > > Rajat > > >> extern bool iommu_dma_forcedac; >> >> #else /* CONFIG_IOMMU_DMA */ >> @@ -54,6 +52,11 @@ static inline void iommu_setup_dma_ops(struct device *dev, u64 dma_base, >> { >> } >> >> +static inline int iommu_dma_init_fq(struct iommu_domain *domain) >> +{ >> + return -EINVAL; >> +} >> + >> static inline int iommu_get_dma_cookie(struct iommu_domain *domain) >> { >> return -ENODEV; >> -- >> 2.25.1 >>
next prev parent reply other threads:[~2021-08-09 19:59 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 17:15 [PATCH v3 00/25] iommu: Refactor DMA domain strictness Robin Murphy 2021-08-04 17:15 ` [PATCH v3 01/25] iommu: Pull IOVA cookie management into the core Robin Murphy 2021-08-04 18:52 ` Heiko Stübner 2021-08-05 7:18 ` Marek Szyprowski 2021-08-05 9:15 ` Yoshihiro Shimoda 2021-08-04 17:15 ` [PATCH v3 02/25] iommu/amd: Drop IOVA cookie management Robin Murphy 2021-08-05 7:37 ` kernel test robot 2021-08-05 9:37 ` Robin Murphy 2021-08-04 17:15 ` [PATCH v3 03/25] iommu/arm-smmu: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 04/25] iommu/vt-d: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 05/25] iommu/exynos: " Robin Murphy 2021-08-05 7:19 ` Marek Szyprowski 2021-08-04 17:15 ` [PATCH v3 06/25] iommu/ipmmu-vmsa: " Robin Murphy 2021-08-05 9:15 ` Yoshihiro Shimoda 2021-08-04 17:15 ` [PATCH v3 07/25] iommu/mtk: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 08/25] iommu/rockchip: " Robin Murphy 2021-08-04 18:53 ` Heiko Stübner 2021-08-04 17:15 ` [PATCH v3 09/25] iommu/sprd: " Robin Murphy 2021-08-06 2:15 ` Chunyan Zhang 2021-08-04 17:15 ` [PATCH v3 10/25] iommu/sun50i: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 11/25] iommu/virtio: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 12/25] iommu/dma: Unexport " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 13/25] iommu/dma: Remove redundant "!dev" checks Robin Murphy 2021-08-04 17:15 ` [PATCH v3 14/25] iommu: Indicate queued flushes via gather data Robin Murphy 2021-08-04 17:15 ` [PATCH v3 15/25] iommu/io-pgtable: Remove non-strict quirk Robin Murphy 2021-08-04 17:15 ` [PATCH v3 16/25] iommu: Introduce explicit type for non-strict DMA domains Robin Murphy 2021-08-04 17:15 ` [PATCH v3 17/25] iommu/amd: Prepare for multiple DMA domain types Robin Murphy 2021-08-04 17:15 ` [PATCH v3 18/25] iommu/arm-smmu: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 19/25] iommu/vt-d: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 20/25] iommu: Express DMA strictness via the domain type Robin Murphy 2021-08-04 17:15 ` [PATCH v3 21/25] iommu: Expose DMA domain strictness via sysfs Robin Murphy 2021-08-04 17:15 ` [PATCH v3 22/25] iommu: Only log strictness for DMA domains Robin Murphy 2021-08-04 17:15 ` [PATCH v3 23/25] iommu: Merge strictness and domain type configs Robin Murphy 2021-08-06 9:15 ` John Garry 2021-08-04 17:15 ` [PATCH v3 24/25] iommu/dma: Factor out flush queue init Robin Murphy 2021-08-09 12:52 ` Will Deacon 2021-08-09 14:47 ` Robin Murphy 2021-08-09 19:05 ` Rajat Jain 2021-08-09 19:59 ` Robin Murphy [this message] 2021-08-09 20:15 ` Rajat Jain 2021-08-04 17:15 ` [PATCH v3 25/25] iommu: Allow enabling non-strict mode dynamically Robin Murphy 2021-08-09 12:49 ` Will Deacon 2021-08-09 13:40 ` Robin Murphy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=00baf83a-5eb3-4d72-309c-5adfd3242c07@arm.com \ --to=robin.murphy@arm.com \ --cc=baolu.lu@linux.intel.com \ --cc=chenxiang66@hisilicon.com \ --cc=dianders@chromium.org \ --cc=iommu@lists.linux-foundation.org \ --cc=john.garry@huawei.com \ --cc=joro@8bytes.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rajatja@google.com \ --cc=suravee.suthikulpanit@amd.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).