On Tue, Mar 20, 2018 at 04:16:00PM +0100, Christoph Hellwig wrote:
> On Tue, Mar 20, 2018 at 11:25:21AM +, Konrad Rzeszutek Wilk wrote:
> > Are you testing with swiotlb=force?
>
> I've done swiotlb=force testing with earlier versions, and otherwise
> relied on a VM with more the 4gb of memory
On Tue, Mar 20, 2018 at 11:25:21AM +, Konrad Rzeszutek Wilk wrote:
> Are you testing with swiotlb=force?
I've done swiotlb=force testing with earlier versions, and otherwise
relied on a VM with more the 4gb of memory and emulated devices
without 64-bit capability.
_
On Tue, Mar 20, 2018, 5:03 AM Ingo Molnar wrote:
>
> * Christoph Hellwig wrote:
>
> > On Tue, Mar 20, 2018 at 09:37:51AM +0100, Ingo Molnar wrote:
> > > > git://git.infradead.org/users/hch/misc.git dma-direct-x86
> > >
> > > Btw., what's the upstreaming route for these patches?
> > >
> > > While
* Christoph Hellwig wrote:
> On Tue, Mar 20, 2018 at 09:37:51AM +0100, Ingo Molnar wrote:
> > > git://git.infradead.org/users/hch/misc.git dma-direct-x86
> >
> > Btw., what's the upstreaming route for these patches?
> >
> > While it's a multi-arch series it's all pretty x86-heavy as well so we
On Tue, Mar 20, 2018 at 09:37:51AM +0100, Ingo Molnar wrote:
> > git://git.infradead.org/users/hch/misc.git dma-direct-x86
>
> Btw., what's the upstreaming route for these patches?
>
> While it's a multi-arch series it's all pretty x86-heavy as well so we can
> host it
> in -tip (in tip:core/dm
* Christoph Hellwig wrote:
> On Mon, Mar 19, 2018 at 11:27:37AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Mon, Mar 19, 2018 at 11:38:12AM +0100, Christoph Hellwig wrote:
> > > Hi all,
> > >
> > > this series switches the x86 code the the dma-direct implementation
> > > for direct (non-iommu) d
On Mon, Mar 19, 2018 at 11:27:37AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 19, 2018 at 11:38:12AM +0100, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series switches the x86 code the the dma-direct implementation
> > for direct (non-iommu) dma and the generic swiotlb ops. This incl
On Mon, Mar 19, 2018 at 11:38:12AM +0100, Christoph Hellwig wrote:
> Hi all,
>
> this series switches the x86 code the the dma-direct implementation
> for direct (non-iommu) dma and the generic swiotlb ops. This includes
> getting rid of the special ops for the AMD memory encryption case and
> th
On Mon, 19 Mar 2018, Christoph Hellwig wrote:
> Hi all,
>
> this series switches the x86 code the the dma-direct implementation
> for direct (non-iommu) dma and the generic swiotlb ops. This includes
> getting rid of the special ops for the AMD memory encryption case and
> the STA2x11 SOC. The
On 3/19/2018 5:38 AM, Christoph Hellwig wrote:
> Hi all,
>
> this series switches the x86 code the the dma-direct implementation
> for direct (non-iommu) dma and the generic swiotlb ops. This includes
> getting rid of the special ops for the AMD memory encryption case and
> the STA2x11 SOC. The
Hi all,
this series switches the x86 code the the dma-direct implementation
for direct (non-iommu) dma and the generic swiotlb ops. This includes
getting rid of the special ops for the AMD memory encryption case and
the STA2x11 SOC. The generic implementations are based on the x86
code, so they
11 matches
Mail list logo
