Quoting Chris Wilson (2017-11-14 13:19:24) > A new context assumes that all of its registers are in the default state > when it is created. What may happen is that a register written by one > context may leak into the second, causing mass confusion. > > v2: extend back to Sandybridge, ignore non-priv registers that are not > context-saved (remind me what this test is all about!!!) > v3: Check context preserves registers across suspend/hibernate and > resets. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > --- > + igt_subtest_f("%s-unsafe", e->name) { > + igt_require(platform_validation); > + isolation(fd, engine, DIRTY2 | DIRTY1 | UNSAFE); > + } I guess the consensus is toward deleting the unsafe variants and doing a more substantial task for p/o validation. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx