[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZJeRomcJjDqDv9q@infradead.org>
Date: Mon, 15 Nov 2021 05:19:02 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joerg Roedel <joro@...tes.org>,
Alex Williamson <alex.williamson@...hat.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Jason Gunthorpe <jgg@...dia.com>,
Kevin Tian <kevin.tian@...el.com>,
Ashok Raj <ashok.raj@...el.com>,
Chaitanya Kulkarni <kch@...dia.com>, kvm@...r.kernel.org,
rafael@...nel.org, linux-pci@...r.kernel.org,
Cornelia Huck <cohuck@...hat.com>,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
Jacob jun Pan <jacob.jun.pan@...el.com>,
Diana Craciun <diana.craciun@....nxp.com>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH 02/11] driver core: Set DMA ownership during driver
bind/unbind
On Mon, Nov 15, 2021 at 10:05:43AM +0800, Lu Baolu wrote:
> @@ -566,6 +567,12 @@ static int really_probe(struct device *dev, struct device_driver *drv)
> goto done;
> }
>
> + if (!drv->suppress_auto_claim_dma_owner) {
> + ret = iommu_device_set_dma_owner(dev, DMA_OWNER_KERNEL, NULL);
> + if (ret)
> + return ret;
> + }
I'd expect this to go into iommu_setup_dma_ops (and its arm and s390
equivalents), as that is what claims an IOMMU for in-kernel usage
Powered by blists - more mailing lists