From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Flush pending GTT writes before unbinding
Date: Mon, 04 Dec 2017 14:46:58 +0200 [thread overview]
Message-ID: <1512391618.4394.35.camel@linux.intel.com> (raw)
In-Reply-To: <20171204124307.2583-1-chris@chris-wilson.co.uk>
On Mon, 2017-12-04 at 12:43 +0000, Chris Wilson wrote:
> From the shrinker paths, we want to relinquish the GPU and GGTT access to
> the object, releasing the backing storage back to the system for
> swapout. As a part of that process we would unpin the pages, marking
> them for access by the CPU (for the swapout/swapin). However, if that
> process was interrupted after unbind the vma, we missed a flush of the
> inflight GGTT writes before we made that GTT space available again for
> reuse, with the prospect that we would redirect them to another page.
>
> The bug dates back to the introduction of multiple GGTT vma, but the
> code itself dates to commit 02bef8f98d26 ("drm/i915: Unbind closed vma
> for i915_gem_object_unbind()").
>
> Fixes: 02bef8f98d26 ("drm/i915: Unbind closed vma for i915_gem_object_unbind()")
> Fixes: c5ad54cf7dd8 ("drm/i915: Use partial view in mmap fault handler")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: stable@vger.kernel.org
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
next prev parent reply other threads:[~2017-12-04 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 12:43 [PATCH] drm/i915: Flush pending GTT writes before unbinding Chris Wilson
2017-12-04 12:46 ` Joonas Lahtinen [this message]
2017-12-04 13:25 ` [RESEND] " Chris Wilson
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=1512391618.4394.35.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).