Thx Will,
On Mon, Jun 24, 2019 at 6:40 PM Will Deacon wrote:
> > I'll keep my system use the same ASID for SMP + IOMMU :P
>
> You will want a separate allocator for that:
>
> https://lkml.kernel.org/r/20190610184714.6786-2-jean-philippe.bruc...@arm.com
Yes, it is hard to maintain ASID between
From: Rob Clark
When games, browser, or anything using a lot of GPU buffers exits, there
can be many hundreds or thousands of buffers to unmap and free. If the
GPU is otherwise suspended, this can cause arm-smmu to resume/suspend
for each buffer, resulting 5-10 seconds worth of reprogramming
Hi,
On 9/7/19 2:49 PM, Adam Zerella wrote:
warning: symbol 'intel_iommu_gfx_mapped' was not declared. Should it be static?
warning: symbol 'intel_iommu_ops' was not declared. Should it be static?
Squash a couple of Sparse warnings by making these symbols static.
Signed-off-by: Adam Zerella
warning: symbol 'intel_iommu_gfx_mapped' was not declared. Should it be static?
warning: symbol 'intel_iommu_ops' was not declared. Should it be static?
Squash a couple of Sparse warnings by making these symbols static.
Signed-off-by: Adam Zerella
---
drivers/iommu/intel-iommu.c | 6 +++---
1
Despite the widespread and complete failure of Broadwell integrated
graphics when DMAR is enabled, known over the years, we have never been
able to root cause the issue. Instead, we let the failure undermine our
confidence in the iommu system itself when we should be pushing for it to
be always
There was some simple Sparse warnings related to making some
signatures static.
Signed-off-by: Adam Zerella
---
drivers/iommu/amd_iommu.c | 4 ++--
drivers/iommu/amd_iommu_init.c | 12 ++--
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/iommu/amd_iommu.c
