Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: lucas.demarchi@intel.com, rodrigo.vivi@intel.com
Cc: intel-xe@lists.freedesktop.org, riana.tauro@intel.com,
	daniele.ceraolospurio@intel.com, matthew.brost@intel.com,
	michal.wajdeczko@intel.com, badal.nilawar@intel.com,
	Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v6 0/4] Introduce GT runtime suspend/resume
Date: Wed, 22 Oct 2025 15:12:42 +0530	[thread overview]
Message-ID: <20251022094246.3584785-1-raag.jadav@intel.com> (raw)

v2: Drop redundant xe_gt_sanitize() and xe_guc_ct_stop() (Daniele)
    Use runtime naming for guc helpers (Daniele)
    Split xe_guc_ct_enable() helper (Daniele)

v3: Drop redundant logging, add kernel doc (Michal)
    Use runtime naming for ct helpers (Michal)

v4: Split xe_guc_ct_enable() patch (Rodrigo)
    Fix tags (Rodrigo)

v5: Include host_l2_vram workaround (Daniele)
    Reuse xe_guc_submit_enable/disable() helpers (Daniele)

v6: Split sumbit_pause/unpause() helpers for VF and PF (Matthew Brost)
    Assert on runtime suspend if VFs are enabled (Daniele)

Raag Jadav (4):
  drm/xe/vf: Update pause/unpause() helpers with VF naming
  drm/xe/guc_submit: Bring back pause/unpause() helpers
  drm/xe/pm: Assert on runtime suspend if VFs are enabled
  drm/xe/gt: Introduce runtime suspend/resume

 drivers/gpu/drm/xe/xe_gt.c          | 60 +++++++++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_gt.h          |  2 +
 drivers/gpu/drm/xe/xe_gt_sriov_vf.c |  6 +--
 drivers/gpu/drm/xe/xe_guc.c         | 34 ++++++++++++++++
 drivers/gpu/drm/xe/xe_guc.h         |  2 +
 drivers/gpu/drm/xe/xe_guc_ct.c      | 27 +++++++++++++
 drivers/gpu/drm/xe/xe_guc_ct.h      |  2 +
 drivers/gpu/drm/xe/xe_guc_submit.c  | 34 +++++++++++++++-
 drivers/gpu/drm/xe/xe_guc_submit.h  |  6 ++-
 drivers/gpu/drm/xe/xe_pci.c         |  8 ++++
 drivers/gpu/drm/xe/xe_pm.c          | 10 ++---
 drivers/gpu/drm/xe/xe_uc.c          | 28 ++++++++++++++
 drivers/gpu/drm/xe/xe_uc.h          |  2 +
 13 files changed, 209 insertions(+), 12 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-10-22  9:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  9:42 Raag Jadav [this message]
2025-10-22  9:42 ` [PATCH v6 1/4] drm/xe/vf: Update pause/unpause() helpers with VF naming Raag Jadav
2025-10-22 15:23   ` Matthew Brost
2025-10-22 17:01     ` Raag Jadav
2025-10-22 17:16       ` Matthew Brost
2025-10-22 15:29   ` Michal Wajdeczko
2025-10-22  9:42 ` [PATCH v6 2/4] drm/xe/guc_submit: Bring back pause/unpause() helpers Raag Jadav
2025-10-22 15:31   ` Matthew Brost
2025-10-22  9:42 ` [PATCH v6 3/4] drm/xe/pm: Assert on runtime suspend if VFs are enabled Raag Jadav
2025-10-22  9:42 ` [PATCH v6 4/4] drm/xe/gt: Introduce runtime suspend/resume Raag Jadav
2025-10-22 15:38   ` Matthew Brost
2025-10-22 12:36 ` ✓ CI.KUnit: success for Introduce GT runtime suspend/resume (rev4) Patchwork
2025-10-22 14:00 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-22 15:38 ` ✗ Xe.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=20251022094246.3584785-1-raag.jadav@intel.com \
    --to=raag.jadav@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@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