[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180320083751.nrpt64dsmpqbhzc6@gmail.com>
Date: Tue, 20 Mar 2018 09:37:51 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, x86@...nel.org,
Tom Lendacky <thomas.lendacky@....com>,
David Woodhouse <dwmw2@...radead.org>,
Muli Ben-Yehuda <mulix@...ix.org>,
Jon Mason <jdmason@...zu.us>, Joerg Roedel <joro@...tes.org>,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: use generic dma-direct and swiotlb code for x86 V3
* Christoph Hellwig <hch@....de> 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) 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 provide the same functionality.
> >
> > I need to test this on my baremertal and Xen setup - and I lost your
> > git repo URL - any chance you mention point out to me so I can
> > kick of a build?
>
> 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/dma or such), but feel free to handle it yourself as well:
Reviewed-by: Ingo Molnar <mingo@...nel.org>
Thanks,
Ingo
Powered by blists - more mailing lists