Re: [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted

Michael S. Tsirkin writes: > On Thu, Jun 27, 2019 at 10:58:40PM -0300, Thiago Jung Bauermann wrote: >> >> Michael S. Tsirkin writes: >> >> > On Mon, Jun 03, 2019 at 10:13:59PM -0300, Thiago Jung Bauermann wrote: >> >> >> >> >> >> Michael S. Tsirkin writes: >> >> >> >> > On Wed, Apr 17, 2019

Re: [PATCH v8 07/21] iommu/io-pgtable-arm-v7s: Extend MediaTek 4GB Mode

On Thu, 2019-07-11 at 13:31 +0100, Will Deacon wrote: > On Thu, Jul 11, 2019 at 07:53:56PM +0800, Yong Wu wrote: > > On Wed, 2019-07-10 at 15:36 +0100, Will Deacon wrote: > > > On Sat, Jun 29, 2019 at 10:09:13AM +0800, Yong Wu wrote: > > > > MediaTek extend the arm v7s descriptor to support the dra

Re: [PATCH 3/3] fs/core/vmcore: Move sev_active() reference to x86 arch code

On Fri, Jul 12, 2019 at 05:42:49PM +0200, Halil Pasic wrote: > > Will do! I guess I should do the patch against the for-next branch of the > dma-mapping tree. But that branch does not have the s390 support patches > (yet?). > To fix it I need both e67a5ed1f86f and 64e1f0c531d1 "s390/mm: force > s

Re: [PATCH 2/3] DMA mapping: Move SME handling to x86-specific files

While this looks generally good to me, I think we want to split this into three patches: 1) update the swiotlb printk 2) removing the dma-mapping check and printk 3) clean up the mem_encrypt.h interface.

Re: [PATCH 1/3] x86,s390: Move ARCH_HAS_MEM_ENCRYPT definition to arch/Kconfig

On Sat, Jul 13, 2019 at 01:45:52AM -0300, Thiago Jung Bauermann wrote: > powerpc is also going to use this feature, so put it in a generic location. Looks good, even without a third arch using it we should never habe symbols defined under arch/$(ARCH) that are used in common code to start with.