From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
x86@kernel.org, Tom Lendacky <thomas.lendacky@amd.com>,
David Woodhouse <dwmw2@infradead.org>,
Muli Ben-Yehuda <mulix@mulix.org>, Jon Mason <jdmason@kudzu.us>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: use generic dma-direct and swiotlb code for x86 V3
Date: Mon, 19 Mar 2018 16:28:40 +0100 [thread overview]
Message-ID: <20180319152840.GA28041@lst.de> (raw)
In-Reply-To: <20180319152737.GK1110@char.us.oracle.com>
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
next prev parent reply other threads:[~2018-03-19 15:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 10:38 use generic dma-direct and swiotlb code for x86 V3 Christoph Hellwig
[not found] ` <20180319103826.12853-1-hch-jcswGhMUV9g@public.gmane.org>
2018-03-19 10:38 ` [PATCH 01/14] x86: remove X86_PPRO_FENCE Christoph Hellwig
2018-03-19 10:38 ` [PATCH 02/14] x86: remove dma_alloc_coherent_mask Christoph Hellwig
2018-03-19 10:38 ` [PATCH 03/14] x86: use dma-direct Christoph Hellwig
2018-03-19 10:38 ` [PATCH 04/14] x86: use generic swiotlb_ops Christoph Hellwig
2018-03-19 10:38 ` [PATCH 05/14] x86/amd_gart: look at coherent_dma_mask instead of GFP_DMA Christoph Hellwig
2018-03-19 10:38 ` [PATCH 06/14] x86/amd_gart: use dma_direct_{alloc,free} Christoph Hellwig
2018-03-19 10:38 ` [PATCH 07/14] iommu/amd_iommu: " Christoph Hellwig
2018-03-19 10:38 ` [PATCH 08/14] iommu/intel-iommu: cleanup intel_{alloc,free}_coherent Christoph Hellwig
2018-03-19 10:38 ` [PATCH 09/14] x86: remove dma_alloc_coherent_gfp_flags Christoph Hellwig
2018-03-19 10:38 ` [PATCH 10/14] set_memory.h: provide set_memory_{en,de}crypted stubs Christoph Hellwig
[not found] ` <20180319103826.12853-11-hch-jcswGhMUV9g@public.gmane.org>
2018-03-19 14:21 ` Tom Lendacky
2018-03-19 10:38 ` [PATCH 11/14] swiotlb: remove swiotlb_set_mem_attributes Christoph Hellwig
[not found] ` <20180319103826.12853-12-hch-jcswGhMUV9g@public.gmane.org>
2018-03-19 14:41 ` Tom Lendacky
2018-03-19 10:38 ` [PATCH 12/14] dma-direct: handle the memory encryption bit in common code Christoph Hellwig
[not found] ` <20180319103826.12853-13-hch-jcswGhMUV9g@public.gmane.org>
2018-03-19 14:50 ` Tom Lendacky
2018-03-19 15:19 ` Robin Murphy
[not found] ` <dd05dd14-9969-7985-826e-f440c3fc4c08-5wv7dgnIgG8@public.gmane.org>
2018-03-19 15:24 ` Christoph Hellwig
[not found] ` <20180319152442.GA27915-jcswGhMUV9g@public.gmane.org>
2018-03-19 15:37 ` Robin Murphy
[not found] ` <5316b479-7e75-d62f-6b17-b6bece55187c-5wv7dgnIgG8@public.gmane.org>
2018-03-19 15:48 ` Will Deacon
[not found] ` <20180319154832.GD14916-5wv7dgnIgG8@public.gmane.org>
2018-03-19 16:03 ` Christoph Hellwig
[not found] ` <20180319160343.GA29002-jcswGhMUV9g@public.gmane.org>
2018-03-19 16:55 ` Will Deacon
2018-03-19 18:01 ` Catalin Marinas
[not found] ` <20180319180141.w5o6lhknhd6q7ktq-+1aNUgJU5qkijLcmloz0ER/iLCjYCKR+VpNB7YpNyf8@public.gmane.org>
2018-03-19 19:49 ` Christoph Hellwig
[not found] ` <20180319194930.GA3255-jcswGhMUV9g@public.gmane.org>
2018-03-20 16:23 ` Catalin Marinas
2018-03-19 10:38 ` [PATCH 13/14] dma-direct: handle force decryption for dma coherent buffers " Christoph Hellwig
[not found] ` <20180319103826.12853-14-hch-jcswGhMUV9g@public.gmane.org>
2018-03-19 14:51 ` Tom Lendacky
2018-03-19 10:38 ` [PATCH 14/14] swiotlb: remove swiotlb_{alloc,free}_coherent Christoph Hellwig
2018-03-19 14:00 ` use generic dma-direct and swiotlb code for x86 V3 Tom Lendacky
2018-03-19 14:56 ` Thomas Gleixner
2018-03-19 15:27 ` Konrad Rzeszutek Wilk
2018-03-19 15:28 ` Christoph Hellwig [this message]
[not found] ` <20180319152840.GA28041-jcswGhMUV9g@public.gmane.org>
2018-03-20 8:37 ` Ingo Molnar
[not found] ` <20180320083751.nrpt64dsmpqbhzc6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-20 8:44 ` Christoph Hellwig
[not found] ` <20180320084412.GA16337-jcswGhMUV9g@public.gmane.org>
2018-03-20 9:03 ` Ingo Molnar
[not found] ` <20180320090351.2qnwcsauhodrqxdj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-03-20 11:25 ` Konrad Rzeszutek Wilk
[not found] ` <CAPbh3rspsGE3i=WzxC4DL=EDTEbhVZVb29j-fyhAXZRwk=Xncg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-03-20 15:16 ` Christoph Hellwig
[not found] ` <20180320151600.GA23920-jcswGhMUV9g@public.gmane.org>
2018-03-21 14:32 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180319152840.GA28041@lst.de \
--to=hch@lst.de \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jdmason@kudzu.us \
--cc=joro@8bytes.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).