diff options
| author | Rob Clark <robdclark@gmail.com> | 2014-08-09 09:07:25 -0400 |
|---|---|---|
| committer | Rob Clark <robdclark@gmail.com> | 2014-08-26 10:43:31 -0400 |
| commit | 6814dbf9414818861cdc21ba1f9799eb2e339b07 (patch) | |
| tree | f4405ff8a5bc6aa6463479b1dacfce2af9fdd823 | |
| parent | a284e9d14e35b776807c3a40dd1ff1e05429d4a4 (diff) | |
| download | linux-3.4.y-6814dbf9414818861cdc21ba1f9799eb2e339b07.tar.gz | |
drm/msm: avoid flood of kernel logs on faults
87e956e9 changed the fault handler to return -ENOSYS, which causes the
iommu driver to print out a huge splat. Which wouldn't be quite so bad
if nothing ever faulted. But seems like some EXA composite operations
generate quite a lot of (seemingly harmless) faults. That is probably a
userspace problem, but the huge increase in verbosity from iommu fault
dumps makes things kind of unusable.
We probably should actually log *some* message (not conditional on
drm.debug). But ratelimit it.
Signed-off-by: Rob Clark <robdclark@gmail.com>
| -rw-r--r-- | drivers/gpu/drm/msm/msm_iommu.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/gpu/drm/msm/msm_iommu.c b/drivers/gpu/drm/msm/msm_iommu.c index 099af483fdf032..7acdaa5688b77e 100644 --- a/drivers/gpu/drm/msm/msm_iommu.c +++ b/drivers/gpu/drm/msm/msm_iommu.c @@ -27,8 +27,8 @@ struct msm_iommu { static int msm_fault_handler(struct iommu_domain *iommu, struct device *dev, unsigned long iova, int flags, void *arg) { - DBG("*** fault: iova=%08lx, flags=%d", iova, flags); - return -ENOSYS; + pr_warn_ratelimited("*** fault: iova=%08lx, flags=%d\n", iova, flags); + return 0; } static int msm_iommu_attach(struct msm_mmu *mmu, const char **names, int cnt) |