Re: dma_ops_domain_alloc causes kernel 4.1.0-next-20150626+ panic

Hi George, On Wed, Jul 01, 2015 at 01:20:59PM +0800, George Wang wrote: > [root@hp-dl385pg8-09 linux-next]# dmidecode|grep -A16 "System Information" > System Information > Manufacturer: HP > Product Name: ProLiant DL385p Gen8 > Version: Not Specified > Serial Number: 6CU428FNLL >

Re: [PATCH 6/8] iommu/arm-smmu: add support for non-pci devices

On 2015/6/30 19:26, Robin Murphy wrote: > On 26/06/15 09:33, Zhen Lei wrote: >> Now, we only support a master with only one stream id. It will cover most >> hardware platforms and coding so easy. >> >> Please refer Documentation\devicetree\bindings\iommu\iommu.txt on how to >> bind device tree. >>

Re: dma_ops_domain_alloc causes kernel 4.1.0-next-20150626+ panic

On Tue, Jun 30, 2015 at 3:34 AM, Joerg Roedel wrote: > On Tue, Jun 30, 2015 at 01:44:34AM +0800, George Wang wrote: >> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c >> index d3e5e9a..4f6da17 100644 >> --- a/drivers/iommu/amd_iommu.c >> +++ b/drivers/iommu/amd_iommu.c >> @@ -18

Kernel panic on Linux 4.1 with intel_iommu=on

Hardware: Intel Core i5 CPU 650 @ 3.20GHz Intel Ironlake Desktop In order to use VT-d on this computer, I have to use 'intel_iommu=on intel_iommu=igfx_off' to prevent graphics problems and system crash. This problem happens on Linux 3.7 and later versions, including the latest release, Linux 4.1.

dma_ops_domain_alloc causes kernel 4.1.0-next-20150626+ panic

Hi, I am trying to do some tests for kernel 4.1.0-next-20150626+, but panic in amd_iommu_attach_dev. After some digging inside amd_iommu.c, I found the suspecting code: diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c index d3e5e9a..4f6da17 100644 --- a/drivers/iommu/amd_iommu.

Re: [PATCH 3/8] iommu/arm-smmu: fix the values of ARM64_TCR_IRGN0_SHIFT and ARM64_TCR_ORGN0_SHIFT

On Tue, Jun 30, 2015 at 04:57:34AM +0100, leizhen wrote: > On 2015/6/30 1:25, Will Deacon wrote: > > On Fri, Jun 26, 2015 at 09:32:59AM +0100, Zhen Lei wrote: > >> In context descriptor, the offset of IR0 is 8, the offset of OR0 is 10. > >> > >> Signed-off-by: Zhen Lei > >> --- > >> drivers/iommu

Re: [PATCH 6/8] iommu/arm-smmu: add support for non-pci devices

On 26/06/15 09:33, Zhen Lei wrote: Now, we only support a master with only one stream id. It will cover most hardware platforms and coding so easy. Please refer Documentation\devicetree\bindings\iommu\iommu.txt on how to bind device tree. Signed-off-by: Zhen Lei --- arch/arm64/include/asm/de

Re: [PATCH 8/8] iommu/arm-smmu: suppress fault information about CMD_PREFETCH_CONFIG execution

On 2015/6/30 1:49, Will Deacon wrote: > On Fri, Jun 26, 2015 at 09:33:04AM +0100, Zhen Lei wrote: >> Some broken SMMUv3 devices treat CMD_PREFETCH_CONFIG as illegal command, >> it's ugly to print error information. CMD_PREFETCH_CONFIG is just used to >> prefetch the configuration for a specified St

Re: [PATCH 7/8] iommu/arm-smmu: enlarge STRTAB_L1_SZ_SHIFT to support larger sidsize

On 2015/6/30 1:35, Will Deacon wrote: > On Fri, Jun 26, 2015 at 09:33:03AM +0100, Zhen Lei wrote: >> Because we will choose the minimum value between STRTAB_L1_SZ_SHIFT and >> IDR1.SIDSIZE, so enlarge STRTAB_L1_SZ_SHIFT will not impact the platforms >> whose IDR1.SIDSIZE is smaller than old STRTAB_

Re: [PATCH 6/8] iommu/arm-smmu: add support for non-pci devices

On 2015/6/30 1:28, Will Deacon wrote: > On Fri, Jun 26, 2015 at 09:33:02AM +0100, Zhen Lei wrote: >> Now, we only support a master with only one stream id. It will cover most >> hardware platforms and coding so easy. >> >> Please refer Documentation\devicetree\bindings\iommu\iommu.txt on how to >>

Re: dma_ops_domain_alloc causes kernel 4.1.0-next-20150626+ panic

On Tue, Jun 30, 2015 at 11:55:24AM +0800, George Wang wrote: > [ 11.734774] Call Trace: > [ 11.735635] [] __mutex_lock_slowpath+0x91/0x120 > [ 11.737676] [] ? ida_simple_get+0x98/0x100 > [ 11.739682] [] mutex_lock+0x23/0x37 > [ 11.741407] [] amd_iommu_map+0x4a/0x1b0 > [ 11.743293]