From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>,
dri-devel@lists.freedesktop.org,
Nirmoy Das <nirmoy.das@intel.com>
Subject: [Intel-gfx] [PATCH 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm
Date: Tue, 17 Jan 2023 12:53:50 +0100 [thread overview]
Message-ID: <20230117115350.1071-2-nirmoy.das@intel.com> (raw)
In-Reply-To: <20230117115350.1071-1-nirmoy.das@intel.com>
Test like i915_gem_mman_live_selftests/igt_mmap_migrate can cause
dmesg spamming. Use ratelimit api to reduce log rate.
References: https://gitlab.freedesktop.org/drm/intel/-/issues/7038
Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index 8cfed1bef629..25294ddbee46 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -1077,8 +1077,9 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)
}
if (err) {
- drm_dbg(dev, "Unable to make resource CPU accessible(err = %pe)\n",
- ERR_PTR(err));
+ drm_dbg_ratelimited(dev,
+ "Unable to make resource CPU accessible(err = %pe)\n",
+ ERR_PTR(err));
dma_resv_unlock(bo->base.resv);
ret = VM_FAULT_SIGBUS;
goto out_rpm;
--
2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>,
dri-devel@lists.freedesktop.org,
Nirmoy Das <nirmoy.das@intel.com>
Subject: [PATCH 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm
Date: Tue, 17 Jan 2023 12:53:50 +0100 [thread overview]
Message-ID: <20230117115350.1071-2-nirmoy.das@intel.com> (raw)
In-Reply-To: <20230117115350.1071-1-nirmoy.das@intel.com>
Test like i915_gem_mman_live_selftests/igt_mmap_migrate can cause
dmesg spamming. Use ratelimit api to reduce log rate.
References: https://gitlab.freedesktop.org/drm/intel/-/issues/7038
Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
index 8cfed1bef629..25294ddbee46 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm.c
@@ -1077,8 +1077,9 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)
}
if (err) {
- drm_dbg(dev, "Unable to make resource CPU accessible(err = %pe)\n",
- ERR_PTR(err));
+ drm_dbg_ratelimited(dev,
+ "Unable to make resource CPU accessible(err = %pe)\n",
+ ERR_PTR(err));
dma_resv_unlock(bo->base.resv);
ret = VM_FAULT_SIGBUS;
goto out_rpm;
--
2.39.0
next prev parent reply other threads:[~2023-01-17 11:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 11:53 [Intel-gfx] [PATCH 1/2] drm/print: Add drm_dbg_ratelimited Nirmoy Das
2023-01-17 11:53 ` Nirmoy Das
2023-01-17 11:53 ` Nirmoy Das [this message]
2023-01-17 11:53 ` [PATCH 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm Nirmoy Das
2023-01-17 11:59 ` [Intel-gfx] " Andrzej Hajda
2023-01-17 13:56 ` Andi Shyti
2023-01-17 11:58 ` [Intel-gfx] [PATCH 1/2] drm/print: Add drm_dbg_ratelimited Andrzej Hajda
2023-01-17 11:58 ` Andrzej Hajda
2023-01-17 12:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] " Patchwork
2023-01-17 13:55 ` [Intel-gfx] [PATCH 1/2] " Andi Shyti
2023-01-17 13:55 ` Andi Shyti
2023-02-10 11:46 ` Andi Shyti
2023-02-10 11:46 ` Andi Shyti
2023-01-17 14:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2023-01-17 14:49 ` [Intel-gfx] [PATCH 1/2] " Sam Ravnborg
2023-01-17 14:49 ` Sam Ravnborg
2023-01-17 15:03 ` [Intel-gfx] " Das, Nirmoy
2023-01-17 15:03 ` Das, Nirmoy
2023-01-17 21:19 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2023-10-10 21:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/print: Add drm_dbg_ratelimited (rev2) Patchwork
2023-10-10 21:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-10 21:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-11 9:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-10-13 8:40 [Intel-gfx] [PATCH 1/2] drm/print: Add drm_dbg_ratelimited Nirmoy Das
2022-10-13 8:40 ` [Intel-gfx] [PATCH 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm Nirmoy Das
2022-11-17 11:25 ` Matthew Auld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230117115350.1071-2-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.