Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, umesh.nerlige.ramappa@intel.com,
	riana.tauro@intel.com
Subject: [PATCH 0/3] Suspend, resume, and d3cold tweaks
Date: Mon, 28 Oct 2024 17:32:21 -0700	[thread overview]
Message-ID: <20241029003224.2257439-1-matthew.brost@intel.com> (raw)

Some low hanging issues to improve suspend, resume, and d3cold.

On BMG xe_pm.d3cold-multiple-execs went from taking ~200s to ~60s.

This will also pave the way to spliting GuC CT state into multiple
BOs mixing system and VRAM placememts. 

Matthew Brost (3):
  drm/xe: Add XE_BO_FLAG_PINNED_WONTNEED
  drm/xe: Restore system memory GGTT mappings
  drm/xe: Add XE_BO_FLAG_PINNED_NEED_LOAD

 drivers/gpu/drm/xe/xe_bo.c                 |  44 +++++---
 drivers/gpu/drm/xe/xe_bo.h                 |   2 +
 drivers/gpu/drm/xe/xe_bo_evict.c           | 118 ++++++++++++++++-----
 drivers/gpu/drm/xe/xe_ggtt.c               |   2 +-
 drivers/gpu/drm/xe/xe_gsc.c                |   1 +
 drivers/gpu/drm/xe/xe_gsc_proxy.c          |   1 +
 drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c |   1 +
 drivers/gpu/drm/xe/xe_guc_ads.c            |   3 +-
 drivers/gpu/drm/xe/xe_guc_ct.c             |   3 +-
 drivers/gpu/drm/xe/xe_guc_log.c            |   3 +-
 drivers/gpu/drm/xe/xe_guc_pc.c             |   3 +-
 drivers/gpu/drm/xe/xe_huc.c                |   1 +
 drivers/gpu/drm/xe/xe_hw_engine.c          |   1 +
 drivers/gpu/drm/xe/xe_lmtt.c               |   1 +
 drivers/gpu/drm/xe/xe_lrc.c                |   3 +
 drivers/gpu/drm/xe/xe_memirq.c             |   1 +
 drivers/gpu/drm/xe/xe_migrate.c            |   1 +
 drivers/gpu/drm/xe/xe_sa.c                 |   3 +-
 drivers/gpu/drm/xe/xe_uc_fw.c              |   1 +
 19 files changed, 145 insertions(+), 48 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-10-29  0:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  0:32 Matthew Brost [this message]
2024-10-29  0:32 ` [PATCH 1/3] drm/xe: Add XE_BO_FLAG_PINNED_WONTNEED Matthew Brost
2024-10-29 13:30   ` Rodrigo Vivi
2024-10-29 14:55     ` Matthew Brost
2024-10-31  4:23       ` Lucas De Marchi
2024-10-31  5:10         ` Matthew Brost
2024-10-29  0:32 ` [PATCH 2/3] drm/xe: Restore system memory GGTT mappings Matthew Brost
2024-10-29  9:44   ` Matthew Auld
2024-10-29 14:57     ` Matthew Brost
2024-10-30 11:53       ` Matthew Auld
2024-10-31  0:49         ` Matthew Brost
2024-10-31  8:44   ` Matthew Auld
2024-10-29  0:32 ` [PATCH 3/3] drm/xe: Add XE_BO_FLAG_PINNED_NEED_LOAD Matthew Brost
2024-10-29  1:07   ` Matthew Brost
2024-10-29  0:44 ` ✓ CI.Patch_applied: success for Suspend, resume, and d3cold tweaks Patchwork
2024-10-29  0:45 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-29  0:46 ` ✓ CI.KUnit: success " Patchwork
2024-10-29  0:58 ` ✓ CI.Build: " Patchwork
2024-10-29  1:00 ` ✓ CI.Hooks: " Patchwork
2024-10-29  1:01 ` ✓ CI.checksparse: " Patchwork
2024-10-29  1:29 ` ✗ CI.BAT: 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=20241029003224.2257439-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@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