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: [PATCH 0/2] Fix CI BAT regressions
Date: Fri, 24 May 2024 14:14:58 -0700	[thread overview]
Message-ID: <20240524211500.1345917-1-umesh.nerlige.ramappa@intel.com> (raw)

Use after free issue is introduced by the below patch.

drm/xe: Add helper to accumulate exec queue runtime

Adding a fix for that in this series.

Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1908
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Umesh Nerlige Ramappa (2):
  drm/xe: Use run_ticks instead of runtime for client stats
  drm/xe: Do not access xe file when updating exec queue run_ticks

 drivers/gpu/drm/xe/xe_device_types.h     |  4 ++--
 drivers/gpu/drm/xe/xe_drm_client.c       |  9 ++++++---
 drivers/gpu/drm/xe/xe_exec_queue.c       | 15 ++++++---------
 drivers/gpu/drm/xe/xe_exec_queue.h       |  2 +-
 drivers/gpu/drm/xe/xe_exec_queue_types.h |  4 ++++
 drivers/gpu/drm/xe/xe_execlist.c         |  2 +-
 drivers/gpu/drm/xe/xe_guc_submit.c       |  2 +-
 7 files changed, 21 insertions(+), 17 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-05-24 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 21:14 Umesh Nerlige Ramappa [this message]
2024-05-24 21:14 ` [PATCH 1/2] drm/xe: Use run_ticks instead of runtime for client stats Umesh Nerlige Ramappa
2024-05-24 21:15 ` [PATCH 2/2] drm/xe: Do not access xe file when updating exec queue run_ticks Umesh Nerlige Ramappa
2024-05-24 22:09 ` ✓ CI.Patch_applied: success for Fix CI BAT regressions Patchwork
2024-05-24 22:09 ` ✓ CI.checkpatch: " Patchwork
2024-05-24 22:10 ` ✓ CI.KUnit: " Patchwork
2024-05-24 22:22 ` ✓ CI.Build: " Patchwork
2024-05-24 22:24 ` ✓ CI.Hooks: " Patchwork
2024-05-24 22:26 ` ✓ CI.checksparse: " Patchwork
2024-05-24 22:48 ` ✓ CI.BAT: " Patchwork
2024-05-27 13:53 ` ✓ 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=20240524211500.1345917-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