RE: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI

2015-01-13 Thread Wu, Feng
> -Original Message- > From: Radim Kr?má? [mailto:rkrc...@redhat.com] > Sent: Wednesday, January 14, 2015 12:17 AM > To: Wu, Feng > Cc: Paolo Bonzini; t...@linutronix.de; mi...@redhat.com; h...@zytor.com; > x...@kernel.org; g...@kernel.org; dw...@infradead.org; j...@8bytes.org; > alex.wil

Re: [PATCH v3 00/19] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

2015-01-13 Thread Javier Martinez Canillas
On 01/14/2015 01:19 AM, Javier Martinez Canillas wrote: > > I dug further on this issue and found that the cause is that the exynos_mixer > driver needs some clocks (CLK_HDMI and CLK_SCLK_HDMI) grabbed by exynos_hdmi > to be kept enabled after hdmi_poweroff (drivers/gpu/drm/exynos/exynos_hdmi.c).

Re: [PATCH v3 00/19] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

2015-01-13 Thread Javier Martinez Canillas
Hello Joonyoung, On 01/13/2015 06:24 AM, Joonyoung Shim wrote: >> >> Yes, I was not able to trigger that by running modetest but by turning off >> my HDMI monitor and then turning it on again. When the monitor is turned >> on then I see a "Power domain power-domain disable failed" and the impreci

Re: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI

2015-01-13 Thread Radim Kr?má?
2015-01-13 00:27+, Wu, Feng: > > On 09/01/2015 15:54, Radim Krčmář wrote: > > > There are two points relevant to this patch in new KVM's implementation, > > > ("KVM: x86: amend APIC lowest priority arbitration", > > > https://lkml.org/lkml/2015/1/9/362) > > > > > > 1) lowest priority depends o

Re: [RFC PATCH 0/5] arm64: IOMMU-backed DMA mapping

2015-01-13 Thread Yingjoe Chen
On Mon, 2015-01-12 at 20:48 +, Robin Murphy wrote: > Hi all, > > Whilst it's a long way off perfect, this has reached the point of being > functional and stable enough to be useful, so here it is. The core > consists of the meat of the arch/arm implementation modified to remove > the assumptio

Re: [RFC PATCH 0/5] arm64: IOMMU-backed DMA mapping

2015-01-13 Thread Robin Murphy
On 13/01/15 08:02, Yingjoe Chen wrote: On Mon, 2015-01-12 at 20:48 +, Robin Murphy wrote: Hi all, Whilst it's a long way off perfect, this has reached the point of being functional and stable enough to be useful, so here it is. The core consists of the meat of the arch/arm implementation mo

Re: [PATCH v8 02/10] iommu/vt-d: Items required for kdump

2015-01-13 Thread Joerg Roedel
On Tue, Jan 13, 2015 at 04:12:29PM +0800, Li, ZhenHua wrote: > Current status: > 1. Use old root entry table, > 2. Copy old context entry tables. > 3. Copy old page tables. > 4. Allocate new page table when device driver is loading. > > I remember the progress we discussed was this. Checking the

Re: [RFC PATCH 0/5] arm64: IOMMU-backed DMA mapping

2015-01-13 Thread Robin Murphy
On 13/01/15 11:08, Stefano Stabellini wrote: On Mon, 12 Jan 2015, Robin Murphy wrote: Hi all, Whilst it's a long way off perfect, this has reached the point of being functional and stable enough to be useful, so here it is. The core consists of the meat of the arch/arm implementation modified t

Re: [PATCH v8 02/10] iommu/vt-d: Items required for kdump

2015-01-13 Thread Baoquan He
On 01/12/15 at 10:29am, Vivek Goyal wrote: > On Mon, Jan 12, 2015 at 04:22:08PM +0100, Joerg Roedel wrote: > > It looks like you are still copying the io-page-tables from the old > > kernel into the kdump kernel, is that right? With the approach that was > > proposed you only need to copy over the

Re: [PATCH RESEND] dma-mapping: tidy up dma_parms default handling

2015-01-13 Thread Marek Szyprowski
Hello, On 2015-01-09 17:56, Robin Murphy wrote: Many DMA controllers and other devices set max_segment_size to indicate their scatter-gather capability, but have no interest in segment_boundary_mask. However, the existence of a dma_parms structure precludes the use of any default value, leaving

Re: [RFC PATCH 0/5] arm64: IOMMU-backed DMA mapping

2015-01-13 Thread Stefano Stabellini
On Mon, 12 Jan 2015, Robin Murphy wrote: > Hi all, > > Whilst it's a long way off perfect, this has reached the point of being > functional and stable enough to be useful, so here it is. The core > consists of the meat of the arch/arm implementation modified to remove > the assumption of PAGE_SIZE

Re: [PATCH v3 00/19] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

2015-01-13 Thread Javier Martinez Canillas
Hello Joonyoung, On 01/13/2015 09:40 AM, Joonyoung Shim wrote: >>> >> These are the changes I have now [0]. Please let me know what you think. >>> >> >> > >> > Good, it's working with your patch without u-boot changes and reverting >> > of commit 2ed127697eb. >> > > But i also get stripe hdmi out

Re: [PATCH v3 00/19] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

2015-01-13 Thread Javier Martinez Canillas
Hello Joonyoung, On 01/13/2015 06:24 AM, Joonyoung Shim wrote: >> >> Also, the SW_ACLK_300_DISP1 and USER_ACLK_300_DISP1 are needed for the FIMD >> parent and input clock respectively. Adding those to the clocks list of the >> DISP1 power domain gives me working display + HDMI on my Exynos5800 Pe

Re: [PATCH v3 00/19] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

2015-01-13 Thread Joonyoung Shim
On 01/13/2015 02:24 PM, Joonyoung Shim wrote: > Hi, > > On 01/13/2015 01:09 AM, Javier Martinez Canillas wrote: >> Hello Joonyoung, >> >> On 01/12/2015 07:40 AM, Joonyoung Shim wrote: And also making changes to the clocks in the clk-exynos5420 driver. Can you please explain the rationale

Re: [PATCH v8 02/10] iommu/vt-d: Items required for kdump

2015-01-13 Thread Li, ZhenHua
On 01/12/2015 11:22 PM, Joerg Roedel wrote: On Mon, Jan 12, 2015 at 03:06:20PM +0800, Li, Zhen-Hua wrote: + +#ifdef CONFIG_CRASH_DUMP + +/* + * Fix Crashdump failure caused by leftover DMA through a hardware IOMMU + * + * Fixes the crashdump kernel to deal with an active iommu and legacy + * DMA