Re: clearly mark DMA_OPS support as an architecture feasture

2024-08-26 Thread Jason Wang
On Mon, Aug 26, 2024 at 2:30 PM Christoph Hellwig wrote: > > On Mon, Aug 26, 2024 at 02:27:27PM +0800, Jason Wang wrote: > > Actually I meant, we can extend the virtio_config_ops to allow mapping > > ops there, then simulator and VDUSE can hook the map ops there. > > From a quick glance that feels

Re: clearly mark DMA_OPS support as an architecture feasture

2024-08-26 Thread Jason Wang
On Mon, Aug 26, 2024 at 2:16 PM Jason Wang wrote: > > On Sat, Aug 24, 2024 at 11:58 AM Christoph Hellwig wrote: > > > > Hi all, > > > > we've had a long standing problems where drivers try to hook into the > > DMA_OPS mechanisms to override them for something that is not DMA, or > > to introduce

Re: clearly mark DMA_OPS support as an architecture feasture

2024-08-26 Thread Jason Wang
On Sat, Aug 24, 2024 at 11:58 AM Christoph Hellwig wrote: > > Hi all, > > we've had a long standing problems where drivers try to hook into the > DMA_OPS mechanisms to override them for something that is not DMA, or > to introduce additional dispatching. > > Now that we are not using DMA_OPS suppo

Re: clearly mark DMA_OPS support as an architecture feasture

2024-08-25 Thread Christoph Hellwig
On Mon, Aug 26, 2024 at 02:27:27PM +0800, Jason Wang wrote: > Actually I meant, we can extend the virtio_config_ops to allow mapping > ops there, then simulator and VDUSE can hook the map ops there. >From a quick glance that feels like the right layer of abstraction, although the config part of th

clearly mark DMA_OPS support as an architecture feasture

2024-08-23 Thread Christoph Hellwig
Hi all, we've had a long standing problems where drivers try to hook into the DMA_OPS mechanisms to override them for something that is not DMA, or to introduce additional dispatching. Now that we are not using DMA_OPS support for dma-iommu and can build kernels without DMA_OPS support on many co