Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI 0/2] Fixes and cleanup for per client utilization
Date: Fri, 28 Jun 2024 01:23:46 +0800	[thread overview]
Message-ID: <20240627172348.84991-1-umesh.nerlige.ramappa@intel.com> (raw)

From: root <root@xpumcyp04.jf.intel.com>

Reviewed patches posted here for CI run before merging.

Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Umesh Nerlige Ramappa (2):
  drm/xe: Use a helper to get delta run ticks from the exec queue
  drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP

 drivers/gpu/drm/xe/xe_drm_client.c | 14 +++++++-------
 drivers/gpu/drm/xe/xe_exec_queue.c | 18 ++++++++++++++++++
 drivers/gpu/drm/xe/xe_exec_queue.h |  1 +
 drivers/gpu/drm/xe/xe_hw_engine.c  |  5 +++++
 drivers/gpu/drm/xe/xe_hw_engine.h  |  1 +
 5 files changed, 32 insertions(+), 7 deletions(-)

--
2.34.1

             reply	other threads:[~2024-06-27 17:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 17:23 Umesh Nerlige Ramappa [this message]
2024-06-27 17:23 ` [CI 1/2] drm/xe: Use a helper to get delta run ticks from the exec queue Umesh Nerlige Ramappa
2024-06-27 20:24   ` Lucas De Marchi
2024-06-27 20:31     ` Umesh Nerlige Ramappa
2024-06-27 23:49       ` Umesh Nerlige Ramappa
2024-06-27 17:23 ` [CI 2/2] drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP Umesh Nerlige Ramappa
2024-06-27 20:11   ` Lucas De Marchi
2024-06-27 17:29 ` ✓ CI.Patch_applied: success for Fixes and cleanup for per client utilization Patchwork
2024-06-27 17:29 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-27 17:30 ` ✓ CI.KUnit: success " Patchwork
2024-06-27 17:42 ` ✓ CI.Build: " Patchwork
2024-06-27 17:45 ` ✓ CI.Hooks: " Patchwork
2024-06-27 17:46 ` ✓ CI.checksparse: " Patchwork
2024-06-27 18:09 ` ✓ CI.BAT: " Patchwork
2024-06-27 20:46 ` ✗ 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=20240627172348.84991-1-umesh.nerlige.ramappa@intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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