Re: [PATCH i-g-t] test/gem_mocs_settings: Testing MOCS register settings

From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Antoine <peter.antoine@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] test/gem_mocs_settings: Testing MOCS register settings
Date: Mon, 4 Apr 2016 20:42:40 +0100	[thread overview]
Message-ID: <20160404194240.GD5867@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604041802240.8501@peterant-linux2>

On Mon, Apr 04, 2016 at 06:30:21PM +0100, Peter Antoine wrote:
> >As well as checking for creating new contexts after resume, we also need
> >to check that the register values are preserved across suspend (i.e.
> >that the register state is being saved back into the context image and
> >then restored).
> 
> Ok, I'll add another test case that does this for the render engine
> (the only one that is effected (at the moment) by context save and
> resume.

We do expect that the mocs values for other rings to be preserved across
suspend. Or did I misunderstand you? i.e create-context; bcs; suspend;
bcs should^W must work.
-Chris

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