cpu hot-remove bug

2015-06-15 Thread 范冬冬
Hi maintainer, We found a problem that a panic happen when cpu was hot-removed. We also trace the problem according to the calltrace information. An endless loop happen because value head is not equal to value tail forever in the function qi_check_fault( ). The location code is as follows:

RE: [PATCH v3 0/7] IOMMU/DMA map_resource support for peer-to-peer

2015-06-15 Thread William Davis
> From: Will Davis > > Hi, > > This is the third version of a patchset to add the DMA APIs necessary to > map and unmap a struct resource to and from a PCI device's IOVA domain. > This allows a PCI device to access a peer device's BAR resource when a > hardware IOMMU is enabled. > Bjorn, Dave

[PATCH v4] drm/exynos: fimd: ensure proper hw state in fimd_clear_channel()

2015-06-15 Thread Marek Szyprowski
One should not do any assumptions on the stare of the fimd hardware during driver initialization, so to properly reset fimd before enabling IOMMU, one should ensure that all power domains and clocks are really enabled. This patch adds pm_runtime and clocks management in the fimd_clear_channel() fun

Re: [PATCH v3 (alternative) 1/3] drm/exynos: fimd: ensure proper hw state in fimd_clear_channel()

2015-06-15 Thread Marek Szyprowski
Hello, On 2015-06-12 15:51, Inki Dae wrote: On 2015년 06월 12일 21:10, Inki Dae wrote: On 2015년 06월 12일 18:07, Marek Szyprowski wrote: One should not do any assumptions on the stare of the fimd hardware during driver initialization, so to properly reset fimd before enabling IOMMU, one should ensu

Re: [PATCH v3 (alternative) 1/3] drm/exynos: fimd: ensure proper hw state in fimd_clear_channel()

2015-06-15 Thread Inki Dae
On 2015년 06월 12일 22:00, Marek Szyprowski wrote: > Hello, > > On 2015-06-12 14:10, Inki Dae wrote: >> On 2015년 06월 12일 18:07, Marek Szyprowski wrote: >>> One should not do any assumptions on the stare of the fimd hardware >>> during driver initialization, so to properly reset fimd before enabling >