On Mon, Jan 09, 2017 at 06:52:52PM +0200, Mika Kuoppala wrote:
> Move the invariant parts of context desc setup from execlist init
> to context creation. This is advantageous when we need to
> create different templates based on the context parametrization,
> ie. for svm capable contexts.
>
> Cc:
On Mon, Jan 09, 2017 at 06:52:53PM +0200, Mika Kuoppala wrote:
> +static int i915_gem_context_enable_svm(struct i915_gem_context *ctx)
> +{
> + int ret;
> +
> + if (!HAS_SVM(ctx->i915))
> + return -ENODEV;
How does legacy execbuf work with an svm context? It will write the
ppgt
On Mon, Jan 09, 2017 at 06:52:54PM +0200, Mika Kuoppala wrote:
> From: Jesse Barnes
>
> We just need to pass in an address to execute and some flags, since we
> don't have to worry about buffer relocation or any of the other usual
> stuff. Takes in a fance and returns a fence to be used for
> sy
The WaDisableLSQCROPERFforOCL workaround has the side effect of
disabling an L3SQ optimization that has huge performance implications
and is unlikely to be necessary for the correct functioning of usual
graphic workloads. Userspace is free to re-enable the workaround on
demand, and is generally in
