On 2019.08.09 17:16:18 +0100, Chris Wilson wrote: > Quoting Mika Kuoppala (2019-08-09 17:12:20) > > Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > > > > > As we are phasing out using the GEM context for internal clients that > > > need to manipulate logical context state directly, remove the > > > constructor for the GVT context. We are not using it for anything other > > > than default setup and allocation of an i915_ppgtt. > > > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > > Not familiar with gvt but seems to create similar enough > > context. > > > > Higher priority, not closed and using more strict > > lock. > > I thought they would appreciate the higher priority ;) > > gvt currently doesn't have anyway for it to determine the relative > priority of its guest vs the host, so if we set it too low we impact the > qos of the guest, too high and its affects the qos of the host. Keeping > it at max user though still gives the kernel some leeway to usurp it. > And who knows one day we may get a scheduler. yep, appreciate that. ;) Acked-by: Zhenyu Wang <zhenyuw@xxxxxxxxxxxxxxx> -- Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
