Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Brian Geffon <bgeffon@google.com>,
	Vidya Srinivas <vidya.srinivas@intel.com>
Subject: Re: [PATCH 0/4] drm/i915/dpt: Try to make DPT shrinkable again
Date: Thu, 28 Nov 2024 17:40:50 +0200	[thread overview]
Message-ID: <Z0iPApqoGFAoS53j@intel.com> (raw)
In-Reply-To: <20241127061117.25622-1-ville.syrjala@linux.intel.com>

On Wed, Nov 27, 2024 at 08:11:13AM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Try to make DPT objects shrinakble once again. To overcome
> the earlier suspend/resume issues we'll just make sure all
> DPT VMAs are evicted during suspend, and thus resume won't
> care whether the DPT objects got kicked out or not. 
> 
> The proper solution would perhaps be to do the DPT CPU
> mapping on demand in dpt insert_{page,range}() but that
> would require a bunch of extra thought (especially for
> DPTs allocated from stolen).
> 
> Cc: Brian Geffon <bgeffon@google.com>
> Cc: Vidya Srinivas <vidya.srinivas@intel.com>
> 
> Ville Syrjälä (4):
>   drm/i915: Don't reuse commit_work for the cleanup
>   drm/i915: Intruduce display.wq.cleanup
>   drm/i915/dpt: Evict all DPT VMAs on suspend
>   Revert "drm/i915/dpt: Make DPT object unshrinkable"

Series pushed to drm-intel-next. Thanks Brian and Vidya.

> 
>  drivers/gpu/drm/i915/display/intel_display.c  |  6 +++---
>  .../gpu/drm/i915/display/intel_display_core.h |  3 +++
>  .../drm/i915/display/intel_display_driver.c   |  6 ++++++
>  .../drm/i915/display/intel_display_types.h    |  2 ++
>  drivers/gpu/drm/i915/display/intel_dpt.c      |  4 ++--
>  drivers/gpu/drm/i915/gem/i915_gem_object.h    |  4 +---
>  drivers/gpu/drm/i915/gt/intel_ggtt.c          | 19 ++++++++++++++-----
>  drivers/gpu/drm/i915/gt/intel_gtt.h           |  4 ++--
>  8 files changed, 33 insertions(+), 15 deletions(-)
> 
> -- 
> 2.45.2

-- 
Ville Syrjälä
Intel

      parent reply	other threads:[~2024-11-28 15:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  6:11 [PATCH 0/4] drm/i915/dpt: Try to make DPT shrinkable again Ville Syrjala
2024-11-27  6:11 ` [PATCH 1/4] drm/i915: Don't reuse commit_work for the cleanup Ville Syrjala
2024-11-28  7:43   ` Srinivas, Vidya
2024-11-27  6:11 ` [PATCH 2/4] drm/i915: Intruduce display.wq.cleanup Ville Syrjala
2024-11-28  7:43   ` Srinivas, Vidya
2024-11-27  6:11 ` [PATCH 3/4] drm/i915/dpt: Evict all DPT VMAs on suspend Ville Syrjala
2024-11-27  8:32   ` Srinivas, Vidya
2024-11-28  7:44   ` Srinivas, Vidya
2024-12-02 15:40   ` Brian Geffon
2024-12-03  8:20     ` Ville Syrjälä
2024-12-03  8:25       ` Ville Syrjälä
2024-12-03 15:13         ` Brian Geffon
2024-11-27  6:11 ` [PATCH 4/4] Revert "drm/i915/dpt: Make DPT object unshrinkable" Ville Syrjala
2024-11-27  9:00   ` Brian Geffon
2024-11-28  7:44   ` Srinivas, Vidya
2024-11-27  6:38 ` ✗ Fi.CI.SPARSE: warning for drm/i915/dpt: Try to make DPT shrinkable again Patchwork
2024-11-27  6:55 ` ✓ i915.CI.BAT: success " Patchwork
2024-11-27  8:26 ` ✗ i915.CI.Full: failure " Patchwork
2024-11-27  8:54 ` [PATCH 0/4] " Srinivas, Vidya
2024-11-28 15:40 ` Ville Syrjälä [this message]

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=Z0iPApqoGFAoS53j@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=bgeffon@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vidya.srinivas@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