public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <niranjana.vishwanathapura@intel.com>
Subject: Re: [PATCH 4/5] drm/xe/multi_queue: Use QUEUE_TIMESTAMP as job timestamp for multi-queue
Date: Thu, 9 Apr 2026 14:20:46 -0700	[thread overview]
Message-ID: <adgYLnHbYkLa52Gw@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260409203714.1887402-11-umesh.nerlige.ramappa@intel.com>

On Thu, Apr 09, 2026 at 01:37:19PM -0700, Umesh Nerlige Ramappa wrote:
> Each queue in a multi queue group has a dedicated timestamp counter. Use
> this QUEUE TIMESTAMP register to capture the start timestamp for the
> job.
> 
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_ring_ops.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_ring_ops.c b/drivers/gpu/drm/xe/xe_ring_ops.c
> index cfeb4fc7d217..0eea37c0b4b2 100644
> --- a/drivers/gpu/drm/xe/xe_ring_ops.c
> +++ b/drivers/gpu/drm/xe/xe_ring_ops.c
> @@ -269,8 +269,12 @@ static u32 get_ppgtt_flag(struct xe_sched_job *job)
>  static int emit_copy_timestamp(struct xe_device *xe, struct xe_lrc *lrc,
>  			       u32 *dw, int i)
>  {
> +	const struct xe_reg reg = lrc->multi_queue.valid ?
> +				   RING_QUEUE_TIMESTAMP(0) :
> +				   RING_CTX_TIMESTAMP(0);
> +
>  	dw[i++] = MI_STORE_REGISTER_MEM | MI_SRM_USE_GGTT | MI_SRM_ADD_CS_OFFSET;
> -	dw[i++] = RING_CTX_TIMESTAMP(0).addr;
> +	dw[i++] = reg.addr;
>  	dw[i++] = xe_lrc_ctx_job_timestamp_ggtt_addr(lrc);
>  	dw[i++] = 0;
>  
> @@ -281,7 +285,7 @@ static int emit_copy_timestamp(struct xe_device *xe, struct xe_lrc *lrc,
>  	if (IS_SRIOV_VF(xe)) {
>  		dw[i++] = MI_STORE_REGISTER_MEM | MI_SRM_USE_GGTT |
>  			MI_SRM_ADD_CS_OFFSET;
> -		dw[i++] = RING_CTX_TIMESTAMP(0).addr;
> +		dw[i++] = reg.addr;
>  		dw[i++] = xe_lrc_ctx_timestamp_ggtt_addr(lrc);
>  		dw[i++] = 0;
>  	}
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-04-09 21:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 20:37 [PATCH 0/5] Support run ticks for multi-queue use case Umesh Nerlige Ramappa
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 [this message]
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=adgYLnHbYkLa52Gw@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=niranjana.vishwanathapura@intel.com \
    --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