From: Mikulas Patocka <mpatocka@redhat.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
intel-gfx@lists.freedesktop.org
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: [PATCH] i915: change pr_info to pr_info_ratelimited
Date: Mon, 5 Aug 2024 16:29:52 +0200 (CEST) [thread overview]
Message-ID: <41f16eed-cc12-ad7d-45ae-bb67815d1728@redhat.com> (raw)
Zdenek Kabelac reported that his syslog was flooded with many messages:
Purging GPU memory, 0 pages freed, 0 pages still pinned, 2029 pages left available.
It happened when he was testing the VDO device mapper module (which
requires a lot of kernel memory).
This commit changes the message to be ratelimited, so that it doesn't spam
the syslog.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Reported-by: Zdenek Kabelac <zkabelac@redhat.com>
---
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/drivers/gpu/drm/i915/gem/i915_gem_shrinker.c
===================================================================
--- linux-2.6.orig/drivers/gpu/drm/i915/gem/i915_gem_shrinker.c 2024-03-11 12:53:59.000000000 +0100
+++ linux-2.6/drivers/gpu/drm/i915/gem/i915_gem_shrinker.c 2024-08-05 16:07:49.000000000 +0200
@@ -375,7 +375,7 @@ i915_gem_shrinker_oom(struct notifier_bl
spin_unlock_irqrestore(&i915->mm.obj_lock, flags);
if (freed_pages || available)
- pr_info("Purging GPU memory, %lu pages freed, "
+ pr_info_ratelimited("Purging GPU memory, %lu pages freed, "
"%lu pages still pinned, %lu pages left available.\n",
freed_pages, unevictable, available);
next reply other threads:[~2024-08-05 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:29 Mikulas Patocka [this message]
2024-08-05 15:02 ` ✓ Fi.CI.BAT: success for i915: change pr_info to pr_info_ratelimited Patchwork
2024-08-05 15:02 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-05 23:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-07 14:40 ` [PATCH] " Andi Shyti
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=41f16eed-cc12-ad7d-45ae-bb67815d1728@redhat.com \
--to=mpatocka@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
--cc=zkabelac@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox