Displaying 15 results from an estimated 15 matches for "876945dbf649".
2017 Jan 16
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...that the virtio stuff was bypassing
> > > even with translation enabled (because it wasn't using the DMA API).
> >
> > Could you point out a commit ID?
>
> There has been a fair amount of work in this area recently, but you're
> probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> as the culprit, which is the point at which we started to swizzle DMA
> ops for devices upstream of an SMMU automatically.
>
> > > > A "Fixes:" tag can't hurt here. I then wonder
> > > > might DMA ops ever...
2017 Jan 16
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...that the virtio stuff was bypassing
> > > even with translation enabled (because it wasn't using the DMA API).
> >
> > Could you point out a commit ID?
>
> There has been a fair amount of work in this area recently, but you're
> probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> as the culprit, which is the point at which we started to swizzle DMA
> ops for devices upstream of an SMMU automatically.
>
> > > > A "Fixes:" tag can't hurt here. I then wonder
> > > > might DMA ops ever...
2017 Jan 19
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...39;t using the DMA API).
> > > > > >
> > > > > > Could you point out a commit ID?
> > > > >
> > > > > There has been a fair amount of work in this area recently, but you're
> > > > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > > > as the culprit, which is the point at which we started to swizzle DMA
> > > > > ops for devices upstream of an SMMU automatically.
> > > > >
> > > > > > > > A "Fixes:"...
2017 Jan 19
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...39;t using the DMA API).
> > > > > >
> > > > > > Could you point out a commit ID?
> > > > >
> > > > > There has been a fair amount of work in this area recently, but you're
> > > > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > > > as the culprit, which is the point at which we started to swizzle DMA
> > > > > ops for devices upstream of an SMMU automatically.
> > > > >
> > > > > > > > A "Fixes:"...
2017 Jan 24
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...MA API).
>>>>>>>>
>>>>>>>> Could you point out a commit ID?
>>>>>>>
>>>>>>> There has been a fair amount of work in this area recently, but you're
>>>>>>> probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
>>>>>>> as the culprit, which is the point at which we started to swizzle DMA
>>>>>>> ops for devices upstream of an SMMU automatically.
>>>>>>>
>>>>>>>>>> A "...
2017 Jan 24
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...MA API).
>>>>>>>>
>>>>>>>> Could you point out a commit ID?
>>>>>>>
>>>>>>> There has been a fair amount of work in this area recently, but you're
>>>>>>> probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
>>>>>>> as the culprit, which is the point at which we started to swizzle DMA
>>>>>>> ops for devices upstream of an SMMU automatically.
>>>>>>>
>>>>>>>>>> A "...
2017 Jan 16
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...; even with translation enabled (because it wasn't using the DMA API).
> > > >
> > > > Could you point out a commit ID?
> > >
> > > There has been a fair amount of work in this area recently, but you're
> > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > as the culprit, which is the point at which we started to swizzle DMA
> > > ops for devices upstream of an SMMU automatically.
> > >
> > > > > > A "Fixes:" tag can't hurt here. I then wonde...
2017 Jan 16
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...; even with translation enabled (because it wasn't using the DMA API).
> > > >
> > > > Could you point out a commit ID?
> > >
> > > There has been a fair amount of work in this area recently, but you're
> > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > as the culprit, which is the point at which we started to swizzle DMA
> > > ops for devices upstream of an SMMU automatically.
> > >
> > > > > > A "Fixes:" tag can't hurt here. I then wonde...
2017 Jan 20
0
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...> > > > > > >
> > > > > > > Could you point out a commit ID?
> > > > > >
> > > > > > There has been a fair amount of work in this area recently, but you're
> > > > > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > > > > as the culprit, which is the point at which we started to swizzle DMA
> > > > > > ops for devices upstream of an SMMU automatically.
> > > > > >
> > > > > > > > >...
2017 Jan 24
0
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...;>>>>>
> >>>>>>>> Could you point out a commit ID?
> >>>>>>>
> >>>>>>> There has been a fair amount of work in this area recently, but you're
> >>>>>>> probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> >>>>>>> as the culprit, which is the point at which we started to swizzle DMA
> >>>>>>> ops for devices upstream of an SMMU automatically.
> >>>>>>>
> >>>>>>>...
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
On Fri, Jan 13, 2017 at 05:21:54PM +0000, Will Deacon wrote:
> On Fri, Jan 13, 2017 at 06:46:32PM +0200, Michael S. Tsirkin wrote:
> > On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
> > > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
> > > > On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote:
> > > > > On
2017 Jan 13
2
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
On Fri, Jan 13, 2017 at 05:21:54PM +0000, Will Deacon wrote:
> On Fri, Jan 13, 2017 at 06:46:32PM +0200, Michael S. Tsirkin wrote:
> > On Fri, Jan 13, 2017 at 09:25:22AM +0000, Will Deacon wrote:
> > > On Fri, Jan 13, 2017 at 12:12:56AM +0200, Michael S. Tsirkin wrote:
> > > > On Wed, Jan 11, 2017 at 10:01:39AM +0000, Will Deacon wrote:
> > > > > On
2017 Jan 16
0
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...and only then was it apparent that the virtio stuff was bypassing
> > even with translation enabled (because it wasn't using the DMA API).
>
> Could you point out a commit ID?
There has been a fair amount of work in this area recently, but you're
probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
as the culprit, which is the point at which we started to swizzle DMA
ops for devices upstream of an SMMU automatically.
> > > A "Fixes:" tag can't hurt here. I then wonder
> > > might DMA ops ever use a DMA address which...
2017 Jan 16
0
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...assing
> > > > even with translation enabled (because it wasn't using the DMA API).
> > >
> > > Could you point out a commit ID?
> >
> > There has been a fair amount of work in this area recently, but you're
> > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > as the culprit, which is the point at which we started to swizzle DMA
> > ops for devices upstream of an SMMU automatically.
> >
> > > > > A "Fixes:" tag can't hurt here. I then wonder
> > > >...
2017 Jan 16
0
[PATCH v2 2/2] vring: Force use of DMA API for ARM-based systems
...nabled (because it wasn't using the DMA API).
> > > > >
> > > > > Could you point out a commit ID?
> > > >
> > > > There has been a fair amount of work in this area recently, but you're
> > > > probably after something like 876945dbf649 ("arm64: Hook up IOMMU dma_ops")
> > > > as the culprit, which is the point at which we started to swizzle DMA
> > > > ops for devices upstream of an SMMU automatically.
> > > >
> > > > > > > A "Fixes:" tag can't hurt...