From: "Timur Kristóf" <timur.kristof@gmail.com>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
Marco Crivellari <marco.crivellari@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>,
Alex Deucher <alexander.deucher@amd.com>,
Christian Konig <christian.koenig@amd.com>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>, Kees Cook <kees@kernel.org>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
Ce Sun <cesun102@amd.com>, Tao Zhou <tao.zhou1@amd.com>,
Thadeu Lima de Souza Cascardo <cascardo@igalia.com>,
Hawking Zhang <Hawking.Zhang@amd.com>
Subject: Re: [PATCH] drm/amdgpu: Change system_unbound_wq with system_dfl_wq
Date: Tue, 07 Jul 2026 13:02:37 +0200 [thread overview]
Message-ID: <12766042.8bMQJbFj6T@timur-max> (raw)
In-Reply-To: <20260707093812.109176-1-marco.crivellari@suse.com>
On 2026. július 7., kedd 11:38:12 közép-európai nyári idő Marco Crivellari
wrote:
> system_wq (per-CPU) and system_unbound_wq (unbound) are the older
> workqueue name, replaced by system_{percpu|dfl}_wq.
> The new workqueues have been introduced by:
>
> 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
>
> Usage of older workqueues will now trigger a pr_warn_once() because they are
> marked as deprecated as per commit:
>
> 64d8eae3f895 ("workqueue: Add warnings and fallback if system_{unbound}_wq
> is used")
>
> So change the used workqueue with the newer, keeping the same behavior.
>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
Nice catch, thank you Marco!
Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c index 53be764968e4..95cceed4e971
> 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> @@ -545,7 +545,7 @@ void amdgpu_irq_delegate(struct amdgpu_device *adev,
> unsigned int num_dw)
> {
> amdgpu_ih_ring_write(adev, &adev->irq.ih_soft, entry->iv_entry,
num_dw);
> - queue_work(system_unbound_wq, &adev->irq.ih_soft_work);
> + queue_work(system_dfl_wq, &adev->irq.ih_soft_work);
> }
>
> /**
next prev parent reply other threads:[~2026-07-07 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:38 [PATCH] drm/amdgpu: Change system_unbound_wq with system_dfl_wq Marco Crivellari
2026-07-07 11:02 ` Timur Kristóf [this message]
2026-07-07 18:12 ` Alex Deucher
2026-07-08 6:23 ` Marco Crivellari
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=12766042.8bMQJbFj6T@timur-max \
--to=timur.kristof@gmail.com \
--cc=Hawking.Zhang@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bigeasy@linutronix.de \
--cc=cascardo@igalia.com \
--cc=cesun102@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=simona@ffwll.ch \
--cc=tao.zhou1@amd.com \
--cc=tj@kernel.org \
--cc=tvrtko.ursulin@igalia.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