Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Vidya Srinivas <vidya.srinivas@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: shawn.c.lee@intel.com,
	Ville Syrjala <ville.syrjala@linux.intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/dpt: Make DPT object unshrinkable
Date: Thu, 23 May 2024 09:25:45 +0100	[thread overview]
Message-ID: <5e5660ac-e14b-4759-a6f6-38cc55d37246@ursulin.net> (raw)
In-Reply-To: <20240522152916.1702614-1-vidya.srinivas@intel.com>


On 22/05/2024 16:29, Vidya Srinivas wrote:
> In some scenarios, the DPT object gets shrunk but
> the actual framebuffer did not and thus its still
> there on the DPT's vm->bound_list. Then it tries to
> rewrite the PTEs via a stale CPU mapping. This causes panic.
> 
> Suggested-by: Ville Syrjala <ville.syrjala@linux.intel.com>
> Cc: stable@vger.kernel.org
> Fixes: 0dc987b699ce ("drm/i915/display: Add smem fallback allocation for dpt")
> Signed-off-by: Vidya Srinivas <vidya.srinivas@intel.com>
> ---
>   drivers/gpu/drm/i915/gem/i915_gem_object.h | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_object.h b/drivers/gpu/drm/i915/gem/i915_gem_object.h
> index 3560a062d287..e6b485fc54d4 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_object.h
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_object.h
> @@ -284,7 +284,8 @@ bool i915_gem_object_has_iomem(const struct drm_i915_gem_object *obj);
>   static inline bool
>   i915_gem_object_is_shrinkable(const struct drm_i915_gem_object *obj)
>   {
> -	return i915_gem_object_type_has(obj, I915_GEM_OBJECT_IS_SHRINKABLE);
> +	return i915_gem_object_type_has(obj, I915_GEM_OBJECT_IS_SHRINKABLE) &&
> +		!obj->is_dpt;

Is there a reason i915_gem_object_make_unshrinkable() cannot be used to 
mark the object at a suitable place?

Regards,

Tvrtko

>   }
>   
>   static inline bool

  reply	other threads:[~2024-05-23  8:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 15:24 [PATCH] drm/i915/dpt: Make DPT object unshrinkable Srinivas, Vidya
2024-05-20 16:15 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-05-20 16:26 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-20 16:39 ` [PATCH] " Ville Syrjälä
2024-05-20 17:14   ` Srinivas, Vidya
2024-05-20 16:56 ` Vidya Srinivas
2024-05-22 15:29   ` Vidya Srinivas
2024-05-23  8:25     ` Tvrtko Ursulin [this message]
2024-05-23 11:19       ` Ville Syrjälä
2024-05-23 12:07         ` Tvrtko Ursulin
2024-05-23 12:24           ` Ville Syrjälä
2024-05-23 13:14             ` Tvrtko Ursulin
2024-05-23 13:52               ` Ville Syrjälä
2024-05-20 18:35 ` ✗ Fi.CI.SPARSE: warning for drm/i915/dpt: Make DPT object unshrinkable (rev2) Patchwork
2024-05-20 18:46 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-21  5:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-22 15:58 ` ✗ Fi.CI.BUILD: failure for drm/i915/dpt: Make DPT object unshrinkable (rev3) 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=5e5660ac-e14b-4759-a6f6-38cc55d37246@ursulin.net \
    --to=tursulin@ursulin.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shawn.c.lee@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=vidya.srinivas@intel.com \
    --cc=ville.syrjala@linux.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