From: Aakash Deep Sarkar <aakash.deep.sarkar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: jeevaka.badrappan@intel.com, rodrigo.vivi@intel.com,
matthew.brost@intel.com, carlos.santa@intel.com,
matthew.auld@intel.com, jani.nikula@intel.com,
Aakash Deep Sarkar <aakash.deep.sarkar@intel.com>
Subject: [PATCH v3 8/8] Handle xe_work_period destruction
Date: Fri, 19 Sep 2025 18:38:08 +0000 [thread overview]
Message-ID: <20250919183817.52325-9-aakash.deep.sarkar@intel.com> (raw)
In-Reply-To: <20250919183817.52325-1-aakash.deep.sarkar@intel.com>
This adds the xe_work_period destruction procedure.
We iterate over all entries in the xe::work_period::users
xarray and cancel any pending delayed work. Then destroy
the xarray itself.
Signed-off-by: Aakash Deep Sarkar <aakash.deep.sarkar@intel.com>
---
drivers/gpu/drm/xe/xe_device.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 30d9f2747eab..3b546d92fa03 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -418,6 +418,8 @@ static struct drm_driver driver = {
static void xe_device_destroy(struct drm_device *dev, void *dummy)
{
struct xe_device *xe = to_xe_device(dev);
+ struct xe_user *user = NULL;
+ unsigned long i;
xe_bo_dev_fini(&xe->bo_device);
@@ -433,6 +435,15 @@ static void xe_device_destroy(struct drm_device *dev, void *dummy)
if (xe->destroy_wq)
destroy_workqueue(xe->destroy_wq);
+
+ mutex_lock(&xe->work_period.lock);
+ xa_for_each(&xe->work_period.users, i, user) {
+ if (cancel_delayed_work_sync(&user->delay_work))
+ xe_user_put(user);
+ }
+ xa_destroy(&xe->work_period.users);
+ mutex_unlock(&xe->work_period.lock);
+
ttm_device_fini(&xe->ttm);
}
--
2.49.0
prev parent reply other threads:[~2025-09-19 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:38 [PATCH v3 0/8] [ANDROID]: Add GPU work period support for Xe driver Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 1/8] Add a new xe_user structure Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 2/8] Add xe_gt_clock_interval_to_ns function Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 3/8] drm/xe: Add a trace point for GPU work period Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 4/8] drm/xe: Modify xe_exec_queue_update_run_ticks Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 5/8] Handle xe_user creation and removal Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 6/8] drm/xe: Implement xe_work_period_worker Aakash Deep Sarkar
2025-09-19 18:38 ` [PATCH v3 7/8] drm/xe: Add a Kconfig option for GPU work period Aakash Deep Sarkar
2025-09-19 18:38 ` Aakash Deep Sarkar [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=20250919183817.52325-9-aakash.deep.sarkar@intel.com \
--to=aakash.deep.sarkar@intel.com \
--cc=carlos.santa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jeevaka.badrappan@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.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