Re: [PATCH v5 04/10] vring: Introduce vring_use_dma_api()
From: David Woodhouse <dwmw2@infradead.org>
Date: 2016-02-01 16:11:31
Possibly related (same subject, not in this thread)
- 2016-02-01 · Re: [PATCH v5 04/10] vring: Introduce vring_use_dma_api() · Andy Lutomirski <luto@amacapital.net>
- 2016-02-01 · Re: [PATCH v5 04/10] vring: Introduce vring_use_dma_api() · "Michael S. Tsirkin" <mst@redhat.com>
- 2016-02-01 · Re: [PATCH v5 04/10] vring: Introduce vring_use_dma_api() · David Woodhouse <dwmw2@infradead.org>
- 2016-01-29 · [PATCH v5 04/10] vring: Introduce vring_use_dma_api() · Andy Lutomirski <luto@kernel.org>
On Mon, 2016-02-01 at 07:39 -0800, Andy Lutomirski wrote:
quoted
quoted
Could we have an arch_vring_eschew_dma_api(dev) function which the affected architectures could provide (as a prelude to fixing it so that the DMA API does the right thing for *itself*)?I'm fine with this.I modified vring_use_dma_api to take a vring_virtqueue* parameter to make this easier. I'm a bit torn here. I want to get the mechanism and the Xen part in, and there's unlikely to be much debate on those as a matter of principle. I'd also like to flip as many arches over as possible, but that could be trickier. Let me mull over this.
Let's queue the arch_vring_eschew_dma_api() thing up after this first batch, and not hold it up any further. -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation