From: "Gupta, Varun" <varun.gupta@intel.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <intel-xe@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/pagemap: Drop ratelimiting from dev_unhold_work debug trace
Date: Wed, 23 Sep 2026 14:09:24 +0530 [thread overview]
Message-ID: <48830e07-7399-4d26-9130-06dcaebb3c94@intel.com> (raw)
In-Reply-To: <20260921063310.89D4D1F000FF@smtp.kernel.org>
On 21-Sep-26 12:03 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] drm/pagemap: CPU stall re-introduced by unbounded drm_dbg() loop
> --
>
> commit ea1ff5e58f9772cc1eaec3db21133d24e24bd4f0
> Author: Varun Gupta <varun.gupta@intel.com>
>
> drm/pagemap: Drop ratelimiting from dev_unhold_work debug trace
>
> This commit reverts the use of drm_dbg_ratelimited back to drm_dbg in
> drm_pagemap_dev_unhold_work to avoid "callbacks suppressed" notifications
> from the kernel's ratelimiting subsystem.
>
>> diff --git a/drivers/gpu/drm/drm_pagemap.c b/drivers/gpu/drm/drm_pagemap.c
>> index c66c58f85c345..743988036a5f8 100644
>> --- a/drivers/gpu/drm/drm_pagemap.c
>> +++ b/drivers/gpu/drm/drm_pagemap.c
>> @@ -1102,7 +1102,7 @@ static void drm_pagemap_dev_unhold_work(struct work_struct *work)
>> struct drm_device *drm = dev_hold->drm;
>> struct module *module = drm->driver->fops->owner;
>>
>> - drm_dbg_ratelimited(drm, "Releasing reference on provider device and module.\n");
>> + drm_dbg(drm, "Releasing reference on provider device and module.\n");
> [Severity: Medium]
> Does this code re-introduce a serial console bottleneck and potential CPU stall
> during teardown?
This does not introduce a stall, it is handled by the WQ_UNBOUND change.
This log was ratelimited to
just prevent log flooding but it in turn introduces a suppressed warning.
> When tearing down an unbounded number of DRM pagemaps,
> drm_pagemap_dev_unhold_work() iterates over the entire
> drm_pagemap_unhold_list. If DRM debugging is enabled, drm_dbg() is now
> called for every single entry unconditionally.
>
> If the goal is to prevent the "callbacks suppressed" warning from the
> ratelimiting subsystem, would it be better to drop the repetitive log
> entirely, or perhaps log once outside the loop, rather than reverting
> the CPU stall fix?
>
>> drm_dev_put(drm);
>> module_put(module);
>> kfree(dev_hold);
next prev parent reply other threads:[~2026-09-23 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 6:26 [PATCH] drm/pagemap: Drop ratelimiting from dev_unhold_work debug trace Varun Gupta
2026-09-21 6:33 ` sashiko-bot
2026-09-23 8:39 ` Gupta, Varun [this message]
2026-09-23 7:54 ` Thomas Hellström
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=48830e07-7399-4d26-9130-06dcaebb3c94@intel.com \
--to=varun.gupta@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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