Quoting Chris Wilson (2018-02-20 10:45:16) > 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 (etc) > v3: Check context preserves registers across suspend/hibernate and resets. > v4: Complete the remapping onto the new class:instance > v5: Not like that, like this, try again to use class:instance > v6: Prepare for retrospective gen4 contexts! > v7: Repaint register set name to nonpriv, as this is what bspec calls the > registers that are writable by userspace. > > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk> > Cc: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahti...@linux.intel.com> Regards, Joonas _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
