From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-xe@lists.freedesktop.org, niranjana.vishwanathapura@intel.com
Cc: matthew.brost@intel.com
Subject: [PATCH 0/5] Support run ticks for multi-queue use case
Date: Thu, 9 Apr 2026 13:37:15 -0700 [thread overview]
Message-ID: <20260409203714.1887402-7-umesh.nerlige.ramappa@intel.com> (raw)
In single queue use cases, the CTX TIMESTAMP can be used to track
context run ticks. In multi-queue scenarios the CTX_TIMESTAMP represents
run ticks of all the queues. To determine individual queue run ticks, we
need to use QUEUE TIMESTAMP.
The series adds support to read out QUEUE TIMESTAMP for multi-queue use
cases.
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Umesh Nerlige Ramappa (5):
drm/xe/multi_queue: Store primary queue and position info in LRC
drm/xe/multi_queue: Add helpers to access CS QUEUE TIMESTAMP from lrc
drm/xe/multi_queue: Capture queue run times for active queues
drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for
multi-queue
drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register
drivers/gpu/drm/xe/regs/xe_engine_regs.h | 4 +
drivers/gpu/drm/xe/regs/xe_lrc_layout.h | 3 +
drivers/gpu/drm/xe/xe_exec_queue.c | 8 +-
drivers/gpu/drm/xe/xe_lrc.c | 166 ++++++++++++++++++++---
drivers/gpu/drm/xe/xe_lrc.h | 6 +
drivers/gpu/drm/xe/xe_lrc_types.h | 13 ++
drivers/gpu/drm/xe/xe_reg_whitelist.c | 6 +
drivers/gpu/drm/xe/xe_ring_ops.c | 8 +-
drivers/gpu/drm/xe/xe_trace_lrc.h | 27 ++++
9 files changed, 218 insertions(+), 23 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-09 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 20:37 Umesh Nerlige Ramappa [this message]
2026-04-09 20:37 ` [PATCH 1/5] drm/xe/multi_queue: Store primary queue and position info in LRC Umesh Nerlige Ramappa
2026-04-09 20:59 ` Matthew Brost
2026-04-09 23:30 ` Umesh Nerlige Ramappa
2026-04-13 21:33 ` Niranjana Vishwanathapura
2026-04-09 20:37 ` [PATCH 2/5] drm/xe/multi_queue: Add helpers to access CS QUEUE TIMESTAMP from lrc Umesh Nerlige Ramappa
2026-04-09 21:10 ` Matthew Brost
2026-04-09 21:16 ` Matthew Brost
2026-04-13 21:44 ` Niranjana Vishwanathapura
2026-04-09 20:37 ` [PATCH 3/5] drm/xe/multi_queue: Capture queue run times for active queues Umesh Nerlige Ramappa
2026-04-09 22:00 ` Matthew Brost
2026-04-09 22:23 ` Summers, Stuart
2026-04-09 23:54 ` Umesh Nerlige Ramappa
2026-04-09 23:03 ` Summers, Stuart
2026-04-13 22:09 ` Niranjana Vishwanathapura
2026-04-13 22:19 ` Umesh Nerlige Ramappa
2026-04-13 22:40 ` Niranjana Vishwanathapura
2026-04-09 20:37 ` [PATCH 4/5] drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for multi-queue Umesh Nerlige Ramappa
2026-04-09 21:20 ` Matthew Brost
2026-04-13 19:08 ` Niranjana Vishwanathapura
2026-04-09 20:37 ` [PATCH 5/5] drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register Umesh Nerlige Ramappa
2026-04-13 18:17 ` Niranjana Vishwanathapura
2026-04-14 18:56 ` Umesh Nerlige Ramappa
2026-04-09 20:42 ` ✗ CI.checkpatch: warning for Support run ticks for multi-queue use case Patchwork
2026-04-09 20:44 ` ✗ CI.KUnit: failure " 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=20260409203714.1887402-7-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=niranjana.vishwanathapura@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