Re: [PATCH] drm/i915: Migrate stolen objects before hibernation

From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Imre Deak <imre.deak@linux.intel.com>,
	intel-gfx@lists.freedesktop.org,
	Akash Goel <akash.goel@intel.com>
Subject: Re: [PATCH] drm/i915: Migrate stolen objects before hibernation
Date: Tue, 30 Jun 2015 12:25:54 +0100	[thread overview]
Message-ID: <20150630112554.GK1381@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20150630105402.GQ30960@phenom.ffwll.local>

On Tue, Jun 30, 2015 at 12:54:02PM +0200, Daniel Vetter wrote:
> The gpu should be able so pinned for scanout is the only corner case I can
> think of atm.

Hmm. That's a nuisance. But... We can throw away all the VM bindings
that are unpinned, and then rewrite those that are left with the shmemfs
pages.

It's ugly. On migration back we would have to do a similar trick, and we
need to tell a few white lies to get past some of our internal BUG_ON.
However, as the contents are the same and the PTE writes are atomic into
the GGTT, it should be invisible to the user.

For internally allocated frontbuffers, I was expecting to mark them as
volatile and let them lose their contents across hibernation - because
they will be immediately cleared afterwards (at least so I expect).
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx