From: Lizhi Hou <lizhi.hou@amd.com>
To: "Falkowski, Maciej" <maciej.falkowski@linux.intel.com>,
<ogabbay@kernel.org>, <quic_jhugo@quicinc.com>,
<dri-devel@lists.freedesktop.org>
Cc: <linux-kernel@vger.kernel.org>, <max.zhen@amd.com>,
<sonal.santan@amd.com>, <mario.limonciello@amd.com>
Subject: Re: [PATCH V1] accel/amdxdna: Fix notifier_wq flushing warning
Date: Wed, 14 Jan 2026 09:12:12 -0800 [thread overview]
Message-ID: <c5c0aa8b-c6fc-ea7b-020e-9ab6bf25cc68@amd.com> (raw)
In-Reply-To: <cf84b137-5bf7-4688-82e6-49c185ca9cb6@linux.intel.com>
Applied to drm-misc-next.
On 1/14/26 07:04, Falkowski, Maciej wrote:
> Reviewed-by: Maciej Falkowski <maciej.falkowski@linux.intel.com>
>
> On 1/13/2026 6:36 PM, Lizhi Hou wrote:
>> Create notifier_wq with WQ_MEM_RECLAIM flag to fix the possible warning.
>>
>> workqueue: WQ_MEM_RECLAIM amdxdna_js:drm_sched_free_job_work
>> [gpu_sched] is flushing !WQ_MEM_RECLAIM notifier_wq:0x0
>>
>> Fixes: e486147c912f ("accel/amdxdna: Add BO import and export")
>> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
>> ---
>> drivers/accel/amdxdna/amdxdna_pci_drv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/accel/amdxdna/amdxdna_pci_drv.c
>> b/drivers/accel/amdxdna/amdxdna_pci_drv.c
>> index a7968fd140a9..1c83efb51f7d 100644
>> --- a/drivers/accel/amdxdna/amdxdna_pci_drv.c
>> +++ b/drivers/accel/amdxdna/amdxdna_pci_drv.c
>> @@ -277,7 +277,7 @@ static int amdxdna_probe(struct pci_dev *pdev,
>> const struct pci_device_id *id)
>> fs_reclaim_release(GFP_KERNEL);
>> }
>> - xdna->notifier_wq = alloc_ordered_workqueue("notifier_wq", 0);
>> + xdna->notifier_wq = alloc_ordered_workqueue("notifier_wq",
>> WQ_MEM_RECLAIM);
>> if (!xdna->notifier_wq)
>> return -ENOMEM;
prev parent reply other threads:[~2026-01-14 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 17:36 Lizhi Hou
2026-01-13 18:33 ` Mario Limonciello (AMD) (kernel.org)
2026-01-14 15:04 ` Falkowski, Maciej
2026-01-14 17:12 ` Lizhi Hou [this message]
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=c5c0aa8b-c6fc-ea7b-020e-9ab6bf25cc68@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.falkowski@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=sonal.santan@amd.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
all inboxes | Powered by JetHome®