iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Cc: Tom Lendacky <thomas.lendacky-5C7GfCeVMHo@public.gmane.org>,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Muli Ben-Yehuda <mulix-BzGcCpaT2IbYtjvyW6yDsg@public.gmane.org>,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH 11/14] swiotlb: remove swiotlb_set_mem_attributes
Date: Thu, 15 Mar 2018 13:51:59 -0400	[thread overview]
Message-ID: <20180315175159.GR13391@char.us.oracle.com> (raw)
In-Reply-To: <20180314175213.20256-12-hch-jcswGhMUV9g@public.gmane.org>

On Wed, Mar 14, 2018 at 06:52:10PM +0100, Christoph Hellwig wrote:
> Now that set_memory_decrypted is always available we can just call it
> directly.
> 

Won't this break ARM build?

  parent reply	other threads:[~2018-03-15 17:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 17:51 use generic dma-direct and swiotlb code for x86 V2 Christoph Hellwig
     [not found] ` <20180314175213.20256-1-hch-jcswGhMUV9g@public.gmane.org>
2018-03-14 17:52   ` [PATCH 01/14] x86: remove X86_PPRO_FENCE Christoph Hellwig
2018-03-14 17:52   ` [PATCH 02/14] x86: remove dma_alloc_coherent_mask Christoph Hellwig
2018-03-14 17:52   ` [PATCH 03/14] x86: use dma-direct Christoph Hellwig
     [not found]     ` <20180314175213.20256-4-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15  8:56       ` Thomas Gleixner
2018-03-15 11:53         ` Christoph Hellwig
2018-03-15 12:53           ` Thomas Gleixner
     [not found]             ` <alpine.DEB.2.21.1803151352170.1525-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2018-03-15 13:40               ` Christoph Hellwig
     [not found]                 ` <20180315134028.GA18074-jcswGhMUV9g@public.gmane.org>
2018-03-15 13:45                   ` Thomas Gleixner
2018-03-14 17:52   ` [PATCH 04/14] x86: use generic swiotlb_ops Christoph Hellwig
     [not found]     ` <20180314175213.20256-5-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15  9:00       ` Thomas Gleixner
     [not found]         ` <alpine.DEB.2.21.1803150956300.1525-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2018-03-15 11:54           ` Christoph Hellwig
     [not found]             ` <20180315115426.GB16210-jcswGhMUV9g@public.gmane.org>
2018-03-15 12:52               ` Thomas Gleixner
     [not found]                 ` <alpine.DEB.2.21.1803151351280.1525-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2018-03-15 13:35                   ` Christoph Hellwig
     [not found]                     ` <20180315133530.GA17956-jcswGhMUV9g@public.gmane.org>
2018-03-15 13:48                       ` Thomas Gleixner
2018-03-14 17:52   ` [PATCH 05/14] x86/amd_gart: look at coherent_dma_mask instead of GFP_DMA Christoph Hellwig
     [not found]     ` <20180314175213.20256-6-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15 17:47       ` Konrad Rzeszutek Wilk
2018-03-14 17:52   ` [PATCH 06/14] x86/amd_gart: use dma_direct_{alloc,free} Christoph Hellwig
2018-03-14 17:52   ` [PATCH 07/14] iommu/amd_iommu: " Christoph Hellwig
     [not found]     ` <20180314175213.20256-8-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15 15:30       ` Joerg Roedel
2018-03-14 17:52   ` [PATCH 08/14] iommu/intel-iommu: cleanup intel_{alloc,free}_coherent Christoph Hellwig
2018-03-14 17:52   ` [PATCH 09/14] x86: remove dma_alloc_coherent_gfp_flags Christoph Hellwig
2018-03-14 17:52   ` [PATCH 10/14] set_memory.h: provide set_memory_{en,de}crypted stubs Christoph Hellwig
     [not found]     ` <20180314175213.20256-11-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15 17:50       ` Konrad Rzeszutek Wilk
2018-03-14 17:52   ` [PATCH 11/14] swiotlb: remove swiotlb_set_mem_attributes Christoph Hellwig
     [not found]     ` <20180314175213.20256-12-hch-jcswGhMUV9g@public.gmane.org>
2018-03-15 17:51       ` Konrad Rzeszutek Wilk [this message]
     [not found]         ` <20180315175159.GR13391-he5eyhs8q0BAdwtm4QZOy9BPR1lH4CV8@public.gmane.org>
2018-03-15 17:54           ` Konrad Rzeszutek Wilk
2018-03-14 17:52   ` [PATCH 12/14] dma-direct: handle the memory encryption bit in common code Christoph Hellwig
2018-03-14 17:52   ` [PATCH 13/14] dma-direct: handle force decryption for dma coherent buffers " Christoph Hellwig
2018-03-14 17:52   ` [PATCH 14/14] swiotlb: remove swiotlb_{alloc,free}_coherent Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
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 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

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=20180315175159.GR13391@char.us.oracle.com \
    --to=konrad.wilk-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mulix-BzGcCpaT2IbYtjvyW6yDsg@public.gmane.org \
    --cc=thomas.lendacky-5C7GfCeVMHo@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).