From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI 8/8] dma-buf: Fix dma-fence-chain signaling ordering
Date: Mon, 27 Oct 2025 14:42:52 -0700 [thread overview]
Message-ID: <20251027214252.2455093-9-matthew.brost@intel.com> (raw)
In-Reply-To: <20251027214252.2455093-1-matthew.brost@intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/dma-buf/dma-fence-chain.c | 6 +++---
include/linux/dma-fence-chain.h | 10 +++++-----
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/dma-buf/dma-fence-chain.c b/drivers/dma-buf/dma-fence-chain.c
index a8a90acf4f34..23f5cf467dd1 100644
--- a/drivers/dma-buf/dma-fence-chain.c
+++ b/drivers/dma-buf/dma-fence-chain.c
@@ -119,7 +119,7 @@ static const char *dma_fence_chain_get_timeline_name(struct dma_fence *fence)
return "unbound";
}
-static void dma_fence_chain_irq_work(struct irq_work *work)
+static void dma_fence_chain_work(struct work_struct *work)
{
struct dma_fence_chain *chain;
@@ -137,8 +137,8 @@ static void dma_fence_chain_cb(struct dma_fence *f, struct dma_fence_cb *cb)
struct dma_fence_chain *chain;
chain = container_of(cb, typeof(*chain), cb);
- init_irq_work(&chain->work, dma_fence_chain_irq_work);
- irq_work_queue(&chain->work);
+ INIT_WORK(&chain->work, dma_fence_chain_work);
+ queue_work(system_ordered_wq, &chain->work);
dma_fence_put(f);
}
diff --git a/include/linux/dma-fence-chain.h b/include/linux/dma-fence-chain.h
index 68c3c1e41014..8e88d3d01fe6 100644
--- a/include/linux/dma-fence-chain.h
+++ b/include/linux/dma-fence-chain.h
@@ -11,8 +11,8 @@
#define __LINUX_DMA_FENCE_CHAIN_H
#include <linux/dma-fence.h>
-#include <linux/irq_work.h>
#include <linux/slab.h>
+#include <linux/workqueue.h>
/**
* struct dma_fence_chain - fence to represent an node of a fence chain
@@ -33,18 +33,18 @@ struct dma_fence_chain {
*
* This is used to add the callback for signaling the
* complection of the fence chain. Never used at the same time
- * as the irq work.
+ * as the work.
*/
struct dma_fence_cb cb;
/**
- * @work: irq work item for signaling
+ * @work: work item for signaling
*
- * Irq work structure to allow us to add the callback without
+ * Work structure to allow us to add the callback without
* running into lock inversion. Never used at the same time as
* the callback.
*/
- struct irq_work work;
+ struct work_struct work;
};
spinlock_t lock;
};
--
2.34.1
next prev parent reply other threads:[~2025-10-27 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 21:42 [CI 0/8] Fix dma-fence-array ordering Matthew Brost
2025-10-27 21:42 ` [CI 1/8] drm/xe: Add last fence attachment to TLB invalidation job queues Matthew Brost
2025-10-27 21:42 ` [CI 2/8] drm/xe: Decouple bind queue last fence from TLB invalidations Matthew Brost
2025-10-27 21:42 ` [CI 3/8] drm/xe: Do not wait on TLB invalidations in page fault binds Matthew Brost
2025-10-27 21:42 ` [CI 4/8] drm/xe: Don't allow in fences on zero batch exec or zero binds Matthew Brost
2025-10-27 21:42 ` [CI 5/8] drm/xe: Remove last fence dependecy check from binds Matthew Brost
2025-10-27 21:42 ` [CI 6/8] workqueue: Add ordered workqueue Matthew Brost
2025-10-27 21:42 ` [CI 7/8] dma-buf: Fix dma-fence-array signaling ordering Matthew Brost
2025-10-27 21:42 ` Matthew Brost [this message]
2025-10-27 23:48 ` ✗ CI.checkpatch: warning for Fix dma-fence-array ordering Patchwork
2025-10-27 23:49 ` ✓ CI.KUnit: success " Patchwork
2025-10-28 0:05 ` ✗ CI.checksparse: warning " Patchwork
2025-10-28 0:32 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-28 8:06 ` ✗ Xe.CI.Full: " Patchwork
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=20251027214252.2455093-9-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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