From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Umesh Nerlige Ramappa" <umesh.nerlige.ramappa@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for Support run ticks for multi-queue use case (rev4)
Date: Wed, 06 May 2026 22:41:06 -0000 [thread overview]
Message-ID: <177810726631.45072.7214892834815110406@5ab824fced77> (raw)
In-Reply-To: <20260506223500.3769614-13-umesh.nerlige.ramappa@intel.com>
== Series Details ==
Series: Support run ticks for multi-queue use case (rev4)
URL : https://patchwork.freedesktop.org/series/164654/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
061140b9bc586ae7f40abc1249c97e1cc72d1b9d
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 159ec128161a3199d1cf60186422e7f96f125da5
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Date: Wed May 6 15:35:12 2026 -0700
drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register
In a multi-queue use case, when a job is running on the secondary queue,
the CTX_TIMESTAMP does not reflect the queues run ticks. Instead, we use
the QUEUE TIMESTAMP to check how long the job ran. For user space to see
the run ticks for a secondary queue, whitelist the QUEUE_TIMESTAMP
register.
Compute PR: https://github.com/intel/compute-runtime/pull/923
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
+ /mt/dim checkpatch 9d4d408c460848efac7cd10f041e7c0a12e7c584 drm-intel
e3d1bd30b91d drm/xe/lrc: Use 64 bit ctx timestamp in the LRC snapshot
7153714516e3 drm/xe: Add timestamp_ms to LRC snapshot
55f0f8ad819b drm/xe/lrc: Refactor xe_lrc_timestamp to simplify logic
ff4cdf26fabc drm/xe/multi_queue: Refactor check for multi queue support for engine class
611162926bd8 drm/xe/multi_queue: Store primary LRC and position info in LRC
-:41: WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#41: FILE: drivers/gpu/drm/xe/xe_exec_queue.c:281:
+ q->lrc[idx]->multi_queue.primary_lrc = q->multi_queue.group->primary->lrc[0];
total: 0 errors, 1 warnings, 0 checks, 80 lines checked
837f9f1a3b51 drm/xe/multi_queue: Add helpers to access CS QUEUE TIMESTAMP from lrc
cbbff952d4b1 drm/xe/lrc: Refactor out engine id to hwe conversion
1545a6c50fad drm/xe/multi_queue: Capture queue run times for active queues
65425ea2de26 drm/xe/multi_queue: Add trace event for the multi queue timestamp
-:43: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#43: FILE: drivers/gpu/drm/xe/xe_trace_lrc.h:49:
+ TP_STRUCT__entry(
-:52: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#52: FILE: drivers/gpu/drm/xe/xe_trace_lrc.h:58:
+ TP_fast_assign(
total: 0 errors, 0 warnings, 2 checks, 47 lines checked
c2925e67b228 drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for multi-queue
159ec128161a drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register
next prev parent reply other threads:[~2026-05-06 22:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 22:35 [PATCH v4 00/11] Support run ticks for multi-queue use case Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 01/11] drm/xe/lrc: Use 64 bit ctx timestamp in the LRC snapshot Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 02/11] drm/xe: Add timestamp_ms to " Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 03/11] drm/xe/lrc: Refactor xe_lrc_timestamp to simplify logic Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 04/11] drm/xe/multi_queue: Refactor check for multi queue support for engine class Umesh Nerlige Ramappa
2026-05-07 0:28 ` Niranjana Vishwanathapura
2026-05-06 22:35 ` [PATCH v4 05/11] drm/xe/multi_queue: Store primary LRC and position info in LRC Umesh Nerlige Ramappa
2026-05-07 0:35 ` Niranjana Vishwanathapura
2026-05-07 1:39 ` Niranjana Vishwanathapura
2026-05-06 22:35 ` [PATCH v4 06/11] drm/xe/multi_queue: Add helpers to access CS QUEUE TIMESTAMP from lrc Umesh Nerlige Ramappa
2026-05-07 0:29 ` Niranjana Vishwanathapura
2026-05-06 22:35 ` [PATCH v4 07/11] drm/xe/lrc: Refactor out engine id to hwe conversion Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 08/11] drm/xe/multi_queue: Capture queue run times for active queues Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 09/11] drm/xe/multi_queue: Add trace event for the multi queue timestamp Umesh Nerlige Ramappa
2026-05-07 0:28 ` Niranjana Vishwanathapura
2026-05-06 22:35 ` [PATCH v4 10/11] drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for multi-queue Umesh Nerlige Ramappa
2026-05-06 22:35 ` [PATCH v4 11/11] drm/xe/multi_queue: Whitelist QUEUE_TIMESTAMP register Umesh Nerlige Ramappa
2026-05-06 22:41 ` Patchwork [this message]
2026-05-06 22:42 ` ✓ CI.KUnit: success for Support run ticks for multi-queue use case (rev4) Patchwork
2026-05-06 23:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-07 0:44 ` ✗ Xe.CI.FULL: 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=177810726631.45072.7214892834815110406@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).