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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Others should be preserved across suspend. BUT they are not context saved (I Know!) so any sort of dirty test won't work. The current test will check the other engines values as they are programmed on start-up (with the new patches) and should be preserved (or be reprogrammed) when coming out of *C6/Suspend/Hibernate.

So context save/resume only needs to be tested for the RCS engine. For Now.

Peter.

On Mon, 4 Apr 2016, Chris Wilson wrote:

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



--
   Peter Antoine (Android Graphics Driver Software Engineer)
   ---------------------------------------------------------------------
   Intel Corporation (UK) Limited
   Registered No. 1134945 (England)
   Registered Office: Pipers Way, Swindon SN3 1RJ
   VAT No: 860 2173 47
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux