Re: [net-next PATCH 02/27] swiotlb-xen: Enforce return of DMA_ERROR_CODE in mapping function

2016-10-28 Thread Konrad Rzeszutek Wilk
On Tue, Oct 25, 2016 at 11:36:58AM -0400, Alexander Duyck wrote: > The mapping function should always return DMA_ERROR_CODE when a mapping has > failed as this is what the DMA API expects when a DMA error has occurred. > The current function for mapping a page in Xen was returning either >

Re: [net-next PATCH 02/27] swiotlb-xen: Enforce return of DMA_ERROR_CODE in mapping function

2016-10-28 Thread Konrad Rzeszutek Wilk
On Tue, Oct 25, 2016 at 11:36:58AM -0400, Alexander Duyck wrote: > The mapping function should always return DMA_ERROR_CODE when a mapping has > failed as this is what the DMA API expects when a DMA error has occurred. > The current function for mapping a page in Xen was returning either >

[net-next PATCH 02/27] swiotlb-xen: Enforce return of DMA_ERROR_CODE in mapping function

2016-10-25 Thread Alexander Duyck
The mapping function should always return DMA_ERROR_CODE when a mapping has failed as this is what the DMA API expects when a DMA error has occurred. The current function for mapping a page in Xen was returning either DMA_ERROR_CODE or 0 depending on where it failed. On x86 DMA_ERROR_CODE is 0,

[net-next PATCH 02/27] swiotlb-xen: Enforce return of DMA_ERROR_CODE in mapping function

2016-10-25 Thread Alexander Duyck
The mapping function should always return DMA_ERROR_CODE when a mapping has failed as this is what the DMA API expects when a DMA error has occurred. The current function for mapping a page in Xen was returning either DMA_ERROR_CODE or 0 depending on where it failed. On x86 DMA_ERROR_CODE is 0,