From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com, alex.zuo@intel.com,
jonathan.cavitt@intel.com, joonas.lahtinen@linux.intel.com,
tvrtko.ursulin@ursulin.net, lucas.demarchi@intel.com,
matthew.brost@intel.com, dri-devel@lists.freedesktop.org,
simona.vetter@ffwll.ch
Subject: [PATCH v3 1/6] drm/xe/xe_exec_queue: Add ID param to exec queue struct
Date: Wed, 19 Feb 2025 16:23:35 +0000 [thread overview]
Message-ID: <20250219162340.116499-2-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20250219162340.116499-1-jonathan.cavitt@intel.com>
Add the exec queue id to the exec queue struct. This is useful for
performing a reverse lookup into the xef->exec_queue xarray.
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
---
drivers/gpu/drm/xe/xe_exec_queue.c | 1 +
drivers/gpu/drm/xe/xe_exec_queue_types.h | 2 ++
2 files changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
index 23a9f519ce1c..4a98a5d0e405 100644
--- a/drivers/gpu/drm/xe/xe_exec_queue.c
+++ b/drivers/gpu/drm/xe/xe_exec_queue.c
@@ -709,6 +709,7 @@ int xe_exec_queue_create_ioctl(struct drm_device *dev, void *data,
if (err)
goto kill_exec_queue;
+ q->id = id;
args->exec_queue_id = id;
return 0;
diff --git a/drivers/gpu/drm/xe/xe_exec_queue_types.h b/drivers/gpu/drm/xe/xe_exec_queue_types.h
index 6eb7ff091534..088d838218e9 100644
--- a/drivers/gpu/drm/xe/xe_exec_queue_types.h
+++ b/drivers/gpu/drm/xe/xe_exec_queue_types.h
@@ -55,6 +55,8 @@ struct xe_exec_queue {
struct xe_vm *vm;
/** @class: class of this exec queue */
enum xe_engine_class class;
+ /** @id: exec queue ID as reported during create ioctl */
+ u32 id;
/**
* @logical_mask: logical mask of where job submitted to exec queue can run
*/
--
2.43.0
next prev parent reply other threads:[~2025-02-19 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 16:23 [PATCH v3 0/6] drm/xe/xe_drm_client: Add per drm client reset stats Jonathan Cavitt
2025-02-19 16:23 ` Jonathan Cavitt [this message]
2025-02-19 16:23 ` [PATCH v3 2/6] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header Jonathan Cavitt
2025-02-19 16:23 ` [PATCH v3 3/6] drm/xe/xe_drm_client: Add per drm client pagefault info Jonathan Cavitt
2025-02-19 16:23 ` [PATCH v3 4/6] drm/xe/xe_drm_client: Add per drm client reset stats Jonathan Cavitt
2025-02-19 16:23 ` [PATCH v3 5/6] drm/xe/xe_query: Pass drm file to query funcs Jonathan Cavitt
2025-02-19 16:23 ` [PATCH v3 6/6] drm/xe/xe_query: Add support for per-drm-client reset stat querying Jonathan Cavitt
2025-02-19 17:04 ` ✓ CI.Patch_applied: success for drm/xe/xe_drm_client: Add per drm client reset stats (rev3) Patchwork
2025-02-19 17:05 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-19 17:06 ` ✓ CI.KUnit: success " Patchwork
2025-02-19 17:37 ` ✓ CI.Build: " Patchwork
2025-02-19 17:39 ` ✓ CI.Hooks: " Patchwork
2025-02-19 17:40 ` ✓ CI.checksparse: " Patchwork
2025-02-19 18:07 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-20 15:36 ` ✗ 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=20250219162340.116499-2-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=tvrtko.ursulin@ursulin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.