Re: [PATCH 0/2] virtio: Support encrypted memory on powerpc secure guests

Hmm.. git-send-email forgot to CC Michael Tsirkin, and Thiago; the original author, who is on vacation. Adding them now. RP On Fri, Oct 11, 2019 at 06:25:17PM -0700, Ram Pai wrote: > **We would like the patches to be merged through the virtio tree. Please > review, and ack merging the DMA

[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()

From: Thiago Jung Bauermann In order to safely use the DMA API, virtio needs to know whether DMA addresses are in fact physical addresses and for that purpose, dma_addr_is_phys_addr() is introduced. cc: Benjamin Herrenschmidt cc: David Gibson cc: Michael Ellerman cc: Paul Mackerras cc:

[PATCH 2/2] virtio_ring: Use DMA API if memory is encrypted

From: Thiago Jung Bauermann Normally, virtio enables DMA API with VIRTIO_F_IOMMU_PLATFORM, which must be set by both device and guest driver. However, as a hack, when DMA API returns physical addresses, guest driver can use the DMA API; even though device does not set VIRTIO_F_IOMMU_PLATFORM and

[PATCH 0/2] virtio: Support encrypted memory on powerpc secure guests

**We would like the patches to be merged through the virtio tree. Please review, and ack merging the DMA mapping change through that tree. Thanks!** The memory of powerpc secure guests can't be accessed by the hypervisor / virtio device except for a few memory regions designated as 'shared'.

Re: [PATCH 0/2] iommu/arm-smmu: Add an optional "input-address-size" property

On Fri, Oct 11, 2019 at 10:16:28AM +0100, Robin Murphy wrote: > On 2019-10-11 4:46 am, Nicolin Chen wrote: > > This series of patches add an optional DT property to allow an SoC to > > specify how many bits being physically connected to its SMMU instance, > > depending on the SoC design. > > This

Re: [PATCH v2 3/4] iommu/mediatek: Use writel for TLB range invalidation

On Wed, Oct 09, 2019 at 09:19:02PM +0800, Yong Wu wrote: > Use writel for the register F_MMU_INV_RANGE which is for triggering the > HW work. We expect all the setting(iova_start/iova_end...) have already > been finished before F_MMU_INV_RANGE. > > Signed-off-by: Anan.Sun > Signed-off-by: Yong

Re: [PATCH 3/3] iommu/ipmmu-vmsa: Add utlb_offset_base

Hi Shimoda-san, On Wed, Oct 9, 2019 at 10:27 AM Yoshihiro Shimoda wrote: > Since we will have changed memory mapping of the IPMMU in the future, > this patch adds a utlb_offset_base into struct ipmmu_features > for IMUCTR and IMUASID registers. > No behavior change. > > Signed-off-by: Yoshihiro

Re: [PATCH 2/3] iommu/ipmmu-vmsa: Calculate context registers' offset instead of a macro

Hi Shimoda-san, On Wed, Oct 9, 2019 at 10:27 AM Yoshihiro Shimoda wrote: > Since we will have changed memory mapping of the IPMMU in the future, > this patch uses ipmmu_features values instead of a macro to > calculate context registers offset. No behavior change. > > Signed-off-by: Yoshihiro

Re: [PATCH 1/3] iommu/ipmmu-vmsa: Remove some unused register declarations

Hi Shimoda-san, Thanks for your patch! On Wed, Oct 9, 2019 at 10:27 AM Yoshihiro Shimoda wrote: > To support different registers memory mapping hardware easily > in the future, this patch removes some unused register > declarations. > > Signed-off-by: Yoshihiro Shimoda Reviewed-by: Geert

Re: [RFC PATCH] iommu/vt-d: Fix IOMMU field not populated on device hot re-plug

Hi Baolu, On Friday, October 11, 2019 8:54:09 AM CEST Lu Baolu wrote: > Hi Janusz, > > On 9/3/19 3:41 PM, Janusz Krzysztofik wrote: > > Hi Baolu, > > > > On Tuesday, September 3, 2019 3:29:40 AM CEST Lu Baolu wrote: > >> Hi Janusz, > >> > >> On 9/2/19 4:37 PM, Janusz Krzysztofik wrote: > I

Re: [PATCH v3 1/2] dma-mapping: Add vmap checks to dma_map_single()

On 2019-10-11 6:02 am, Greg Kroah-Hartman wrote: On Thu, Oct 10, 2019 at 03:28:28PM -0700, Kees Cook wrote: As we've seen from USB and other areas[1], we need to always do runtime checks for DMA operating on memory regions that might be remapped. This adds vmap checks (similar to those already

Re: [PATCH 0/2] iommu/arm-smmu: Add an optional "input-address-size" property

On 2019-10-11 4:46 am, Nicolin Chen wrote: This series of patches add an optional DT property to allow an SoC to specify how many bits being physically connected to its SMMU instance, depending on the SoC design. This has come up before, and it doesn't work in general because a single SMMU

Re: [PATCH v3 0/6] ACPI / utils: add new helper for HID/UID match

On Tuesday, October 1, 2019 4:27:19 PM CEST Andy Shevchenko wrote: > There are few users outside of ACPI realm that re-introduce a custom > solution to match ACPI device against HID/UID. Add a generic helper for > them. > > The series is supposed to go via linux-pm tree. > > In v3: > - correct

Re: [PATCH v2] dma-mapping: Move vmap address checks into dma_map_single()

Hi Kees, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the

Re: [RFC PATCH] iommu/vt-d: Fix IOMMU field not populated on device hot re-plug

Hi Janusz, On 9/3/19 3:41 PM, Janusz Krzysztofik wrote: Hi Baolu, On Tuesday, September 3, 2019 3:29:40 AM CEST Lu Baolu wrote: Hi Janusz, On 9/2/19 4:37 PM, Janusz Krzysztofik wrote: I am not saying that keeping data is not acceptable. I just want to check whether there are any other