[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210113115126.GB29376@lst.de>
Date: Wed, 13 Jan 2021 12:51:26 +0100
From: Christoph Hellwig <hch@....de>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Claire Chang <tientzu@...omium.org>, robh+dt@...nel.org,
mpe@...erman.id.au, benh@...nel.crashing.org, paulus@...ba.org,
joro@...tes.org, will@...nel.org, frowand.list@...il.com,
konrad.wilk@...cle.com, boris.ostrovsky@...cle.com,
jgross@...e.com, sstabellini@...nel.org, hch@....de,
m.szyprowski@...sung.com, robin.murphy@....com,
grant.likely@....com, xypron.glpk@....de, treding@...dia.com,
mingo@...nel.org, bauerman@...ux.ibm.com, peterz@...radead.org,
saravanak@...gle.com, rafael.j.wysocki@...el.com,
heikki.krogerus@...ux.intel.com, andriy.shevchenko@...ux.intel.com,
rdunlap@...radead.org, dan.j.williams@...el.com,
bgolaszewski@...libre.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
iommu@...ts.linux-foundation.org, xen-devel@...ts.xenproject.org,
tfiga@...omium.org, drinkcat@...omium.org
Subject: Re: [RFC PATCH v3 2/6] swiotlb: Add restricted DMA pool
On Wed, Jan 06, 2021 at 08:50:03AM +0100, Greg KH wrote:
> > --- a/include/linux/device.h
> > +++ b/include/linux/device.h
> > @@ -413,6 +413,7 @@ struct dev_links_info {
> > * @dma_pools: Dma pools (if dma'ble device).
> > * @dma_mem: Internal for coherent mem override.
> > * @cma_area: Contiguous memory area for dma allocations
> > + * @dma_io_tlb_mem: Internal for swiotlb io_tlb_mem override.
>
> Why does this have to be added here? Shouldn't the platform-specific
> code handle it instead?
The whole code added here is pretty generic. What we need to eventually
do, though is to add a separate dma_device instead of adding more and more
bloat to struct device.
Powered by blists - more mailing lists