* [PATCH 0/2] drm/i915: Better document VM and engine set APIs @ 2021-07-10 21:24 ` Jason Ekstrand 0 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter, Jason Ekstrand As per Daniel's request, this better documents the VM and engine set APIs including some discussion of the deprecation plan. Test-with: 20210710211923.784638-1-jason@jlekstrand.net Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Jason Ekstrand (2): drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice drm/i915/uapi: Add docs about immutability of engine sets and VMs drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++---- include/uapi/drm/i915_drm.h | 39 +++++++++++++++------ 2 files changed, 33 insertions(+), 18 deletions(-) -- 2.31.1 ^ permalink raw reply [flat|nested] 13+ messages in thread
* [Intel-gfx] [PATCH 0/2] drm/i915: Better document VM and engine set APIs @ 2021-07-10 21:24 ` Jason Ekstrand 0 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter As per Daniel's request, this better documents the VM and engine set APIs including some discussion of the deprecation plan. Test-with: 20210710211923.784638-1-jason@jlekstrand.net Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Jason Ekstrand (2): drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice drm/i915/uapi: Add docs about immutability of engine sets and VMs drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++---- include/uapi/drm/i915_drm.h | 39 +++++++++++++++------ 2 files changed, 33 insertions(+), 18 deletions(-) -- 2.31.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH 1/2] drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand @ 2021-07-10 21:24 ` Jason Ekstrand -1 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter, Jason Ekstrand Allowing setting it multiple times brings no real utility to the API, no userspace relies on it, and it does make i915 a tiny bit more complicated. Let's disallow it for now unless someone comes up with a compelling reason to support it. Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> --- drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c index 7d6f52d8a8012..5853737cc79f3 100644 --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c @@ -319,7 +319,6 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, const struct drm_i915_gem_context_param *args) { struct drm_i915_private *i915 = fpriv->dev_priv; - struct i915_address_space *vm; if (args->size) return -EINVAL; @@ -327,17 +326,16 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, if (!HAS_FULL_PPGTT(i915)) return -ENODEV; + if (pc->vm) + return -EINVAL; + if (upper_32_bits(args->value)) return -ENOENT; - vm = i915_gem_vm_lookup(fpriv, args->value); - if (!vm) + pc->vm = i915_gem_vm_lookup(fpriv, args->value); + if (!pc->vm) return -ENOENT; - if (pc->vm) - i915_vm_put(pc->vm); - pc->vm = vm; - return 0; } -- 2.31.1 ^ permalink raw reply related [flat|nested] 13+ messages in thread
* [Intel-gfx] [PATCH 1/2] drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice @ 2021-07-10 21:24 ` Jason Ekstrand 0 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter Allowing setting it multiple times brings no real utility to the API, no userspace relies on it, and it does make i915 a tiny bit more complicated. Let's disallow it for now unless someone comes up with a compelling reason to support it. Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> --- drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c index 7d6f52d8a8012..5853737cc79f3 100644 --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c @@ -319,7 +319,6 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, const struct drm_i915_gem_context_param *args) { struct drm_i915_private *i915 = fpriv->dev_priv; - struct i915_address_space *vm; if (args->size) return -EINVAL; @@ -327,17 +326,16 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, if (!HAS_FULL_PPGTT(i915)) return -ENODEV; + if (pc->vm) + return -EINVAL; + if (upper_32_bits(args->value)) return -ENOENT; - vm = i915_gem_vm_lookup(fpriv, args->value); - if (!vm) + pc->vm = i915_gem_vm_lookup(fpriv, args->value); + if (!pc->vm) return -ENOENT; - if (pc->vm) - i915_vm_put(pc->vm); - pc->vm = vm; - return 0; } -- 2.31.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [PATCH 1/2] drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand @ 2021-07-12 14:30 ` Daniel Vetter -1 siblings, 0 replies; 13+ messages in thread From: Daniel Vetter @ 2021-07-12 14:30 UTC (permalink / raw) To: Jason Ekstrand; +Cc: Daniel Vetter, intel-gfx, dri-devel On Sat, Jul 10, 2021 at 04:24:46PM -0500, Jason Ekstrand wrote: > Allowing setting it multiple times brings no real utility to the API, no > userspace relies on it, and it does make i915 a tiny bit more > complicated. Let's disallow it for now unless someone comes up with a > compelling reason to support it. Maybe mention this is for symmetry with other proto ctx set_param operations, like set_engines. > > Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> > --- > drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++++------- > 1 file changed, 5 insertions(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c > index 7d6f52d8a8012..5853737cc79f3 100644 > --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c > +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c > @@ -319,7 +319,6 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, > const struct drm_i915_gem_context_param *args) > { > struct drm_i915_private *i915 = fpriv->dev_priv; > - struct i915_address_space *vm; > > if (args->size) > return -EINVAL; > @@ -327,17 +326,16 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, > if (!HAS_FULL_PPGTT(i915)) > return -ENODEV; > > + if (pc->vm) > + return -EINVAL; > + > if (upper_32_bits(args->value)) > return -ENOENT; > > - vm = i915_gem_vm_lookup(fpriv, args->value); > - if (!vm) > + pc->vm = i915_gem_vm_lookup(fpriv, args->value); > + if (!pc->vm) > return -ENOENT; > > - if (pc->vm) > - i915_vm_put(pc->vm); > - pc->vm = vm; > - > return 0; > } > > -- > 2.31.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice @ 2021-07-12 14:30 ` Daniel Vetter 0 siblings, 0 replies; 13+ messages in thread From: Daniel Vetter @ 2021-07-12 14:30 UTC (permalink / raw) To: Jason Ekstrand; +Cc: Daniel Vetter, intel-gfx, dri-devel On Sat, Jul 10, 2021 at 04:24:46PM -0500, Jason Ekstrand wrote: > Allowing setting it multiple times brings no real utility to the API, no > userspace relies on it, and it does make i915 a tiny bit more > complicated. Let's disallow it for now unless someone comes up with a > compelling reason to support it. Maybe mention this is for symmetry with other proto ctx set_param operations, like set_engines. > > Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> > --- > drivers/gpu/drm/i915/gem/i915_gem_context.c | 12 +++++------- > 1 file changed, 5 insertions(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_context.c b/drivers/gpu/drm/i915/gem/i915_gem_context.c > index 7d6f52d8a8012..5853737cc79f3 100644 > --- a/drivers/gpu/drm/i915/gem/i915_gem_context.c > +++ b/drivers/gpu/drm/i915/gem/i915_gem_context.c > @@ -319,7 +319,6 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, > const struct drm_i915_gem_context_param *args) > { > struct drm_i915_private *i915 = fpriv->dev_priv; > - struct i915_address_space *vm; > > if (args->size) > return -EINVAL; > @@ -327,17 +326,16 @@ static int set_proto_ctx_vm(struct drm_i915_file_private *fpriv, > if (!HAS_FULL_PPGTT(i915)) > return -ENODEV; > > + if (pc->vm) > + return -EINVAL; > + > if (upper_32_bits(args->value)) > return -ENOENT; > > - vm = i915_gem_vm_lookup(fpriv, args->value); > - if (!vm) > + pc->vm = i915_gem_vm_lookup(fpriv, args->value); > + if (!pc->vm) > return -ENOENT; > > - if (pc->vm) > - i915_vm_put(pc->vm); > - pc->vm = vm; > - > return 0; > } > > -- > 2.31.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
* [PATCH 2/2] drm/i915/uapi: Add docs about immutability of engine sets and VMs 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand @ 2021-07-10 21:24 ` Jason Ekstrand -1 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter, Jason Ekstrand Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> --- include/uapi/drm/i915_drm.h | 39 ++++++++++++++++++++++++++----------- 1 file changed, 28 insertions(+), 11 deletions(-) diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h index e334a8b14ef2d..b6bfbda1258c8 100644 --- a/include/uapi/drm/i915_drm.h +++ b/include/uapi/drm/i915_drm.h @@ -1676,15 +1676,25 @@ struct drm_i915_gem_context_param { */ #define I915_CONTEXT_PARAM_RECOVERABLE 0x8 - /* - * The id of the associated virtual memory address space (ppGTT) of - * this context. Can be retrieved and passed to another context - * (on the same fd) for both to use the same ppGTT and so share - * address layouts, and avoid reloading the page tables on context - * switches between themselves. - * - * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. - */ +/* + * The id of the associated virtual memory address space (ppGTT) of + * this context. Can be retrieved and passed to another context + * (on the same fd) for both to use the same ppGTT and so share + * address layouts, and avoid reloading the page tables on context + * switches between themselves. + * + * The VM id should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. + * + * On GPUs with graphics version 12 and earlier, it may also be set via + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for + * backwards compatibility with old userspace and should be considered + * deprecated. Starting with graphics version 13, it can only be set via + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be + * set once for each context and, once the context has been used with any + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. + * + * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. + */ #define I915_CONTEXT_PARAM_VM 0x9 /* @@ -1700,8 +1710,15 @@ struct drm_i915_gem_context_param { * to specify a gap in the array that can be filled in later, e.g. by a * virtual engine used for load balancing. * - * Setting the number of engines bound to the context to 0, by passing a zero - * sized argument, will revert back to default settings. + * The engine set should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. + * + * On GPUs with graphics version 12 and earlier, it may also be set via + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for + * backwards compatibility with old userspace and should be considered + * deprecated. Starting with graphics version 13, it can only be set via + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be + * set once for each context and, once the context has been used with any + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. * * See struct i915_context_param_engines. * -- 2.31.1 ^ permalink raw reply related [flat|nested] 13+ messages in thread
* [Intel-gfx] [PATCH 2/2] drm/i915/uapi: Add docs about immutability of engine sets and VMs @ 2021-07-10 21:24 ` Jason Ekstrand 0 siblings, 0 replies; 13+ messages in thread From: Jason Ekstrand @ 2021-07-10 21:24 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Daniel Vetter Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> --- include/uapi/drm/i915_drm.h | 39 ++++++++++++++++++++++++++----------- 1 file changed, 28 insertions(+), 11 deletions(-) diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h index e334a8b14ef2d..b6bfbda1258c8 100644 --- a/include/uapi/drm/i915_drm.h +++ b/include/uapi/drm/i915_drm.h @@ -1676,15 +1676,25 @@ struct drm_i915_gem_context_param { */ #define I915_CONTEXT_PARAM_RECOVERABLE 0x8 - /* - * The id of the associated virtual memory address space (ppGTT) of - * this context. Can be retrieved and passed to another context - * (on the same fd) for both to use the same ppGTT and so share - * address layouts, and avoid reloading the page tables on context - * switches between themselves. - * - * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. - */ +/* + * The id of the associated virtual memory address space (ppGTT) of + * this context. Can be retrieved and passed to another context + * (on the same fd) for both to use the same ppGTT and so share + * address layouts, and avoid reloading the page tables on context + * switches between themselves. + * + * The VM id should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. + * + * On GPUs with graphics version 12 and earlier, it may also be set via + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for + * backwards compatibility with old userspace and should be considered + * deprecated. Starting with graphics version 13, it can only be set via + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be + * set once for each context and, once the context has been used with any + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. + * + * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. + */ #define I915_CONTEXT_PARAM_VM 0x9 /* @@ -1700,8 +1710,15 @@ struct drm_i915_gem_context_param { * to specify a gap in the array that can be filled in later, e.g. by a * virtual engine used for load balancing. * - * Setting the number of engines bound to the context to 0, by passing a zero - * sized argument, will revert back to default settings. + * The engine set should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. + * + * On GPUs with graphics version 12 and earlier, it may also be set via + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for + * backwards compatibility with old userspace and should be considered + * deprecated. Starting with graphics version 13, it can only be set via + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be + * set once for each context and, once the context has been used with any + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. * * See struct i915_context_param_engines. * -- 2.31.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: [PATCH 2/2] drm/i915/uapi: Add docs about immutability of engine sets and VMs 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand @ 2021-07-12 14:34 ` Daniel Vetter -1 siblings, 0 replies; 13+ messages in thread From: Daniel Vetter @ 2021-07-12 14:34 UTC (permalink / raw) To: Jason Ekstrand; +Cc: Daniel Vetter, intel-gfx, dri-devel On Sat, Jul 10, 2021 at 04:24:47PM -0500, Jason Ekstrand wrote: > Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > --- > include/uapi/drm/i915_drm.h | 39 ++++++++++++++++++++++++++----------- > 1 file changed, 28 insertions(+), 11 deletions(-) > > diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h > index e334a8b14ef2d..b6bfbda1258c8 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -1676,15 +1676,25 @@ struct drm_i915_gem_context_param { > */ > #define I915_CONTEXT_PARAM_RECOVERABLE 0x8 > > - /* > - * The id of the associated virtual memory address space (ppGTT) of > - * this context. Can be retrieved and passed to another context > - * (on the same fd) for both to use the same ppGTT and so share > - * address layouts, and avoid reloading the page tables on context > - * switches between themselves. > - * > - * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. > - */ > +/* So the annoying thing here is that this way it's not picked up by the kerneldoc machinery. I think what Matt has done is included parameters as an item list in the relevant struct kerneldoc, which seems like the most reasonable thing to do with them. That means some mild duplication for get/set parts, but since we've made the uapi very asymmetric in that, that's probably a feature. > + * The id of the associated virtual memory address space (ppGTT) of > + * this context. Can be retrieved and passed to another context > + * (on the same fd) for both to use the same ppGTT and so share > + * address layouts, and avoid reloading the page tables on context > + * switches between themselves. > + * > + * The VM id should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. > + * > + * On GPUs with graphics version 12 and earlier, it may also be set via > + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for > + * backwards compatibility with old userspace and should be considered > + * deprecated. Starting with graphics version 13, it can only be set via > + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be > + * set once for each context and, once the context has been used with any > + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. > + * > + * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. Again for kerneldoc linking to the struct of the ioctl is probably better, since then you get a link. > + */ > #define I915_CONTEXT_PARAM_VM 0x9 > > /* > @@ -1700,8 +1710,15 @@ struct drm_i915_gem_context_param { > * to specify a gap in the array that can be filled in later, e.g. by a > * virtual engine used for load balancing. > * > - * Setting the number of engines bound to the context to 0, by passing a zero > - * sized argument, will revert back to default settings. > + * The engine set should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. > + * > + * On GPUs with graphics version 12 and earlier, it may also be set via > + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for > + * backwards compatibility with old userspace and should be considered > + * deprecated. Starting with graphics version 13, it can only be set via > + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be > + * set once for each context and, once the context has been used with any > + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. > * > * See struct i915_context_param_engines. Maybe we should push most of the docs for params with structs into the struct's kerneldoc? -Daniel > * > -- > 2.31.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915/uapi: Add docs about immutability of engine sets and VMs @ 2021-07-12 14:34 ` Daniel Vetter 0 siblings, 0 replies; 13+ messages in thread From: Daniel Vetter @ 2021-07-12 14:34 UTC (permalink / raw) To: Jason Ekstrand; +Cc: Daniel Vetter, intel-gfx, dri-devel On Sat, Jul 10, 2021 at 04:24:47PM -0500, Jason Ekstrand wrote: > Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > --- > include/uapi/drm/i915_drm.h | 39 ++++++++++++++++++++++++++----------- > 1 file changed, 28 insertions(+), 11 deletions(-) > > diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h > index e334a8b14ef2d..b6bfbda1258c8 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -1676,15 +1676,25 @@ struct drm_i915_gem_context_param { > */ > #define I915_CONTEXT_PARAM_RECOVERABLE 0x8 > > - /* > - * The id of the associated virtual memory address space (ppGTT) of > - * this context. Can be retrieved and passed to another context > - * (on the same fd) for both to use the same ppGTT and so share > - * address layouts, and avoid reloading the page tables on context > - * switches between themselves. > - * > - * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. > - */ > +/* So the annoying thing here is that this way it's not picked up by the kerneldoc machinery. I think what Matt has done is included parameters as an item list in the relevant struct kerneldoc, which seems like the most reasonable thing to do with them. That means some mild duplication for get/set parts, but since we've made the uapi very asymmetric in that, that's probably a feature. > + * The id of the associated virtual memory address space (ppGTT) of > + * this context. Can be retrieved and passed to another context > + * (on the same fd) for both to use the same ppGTT and so share > + * address layouts, and avoid reloading the page tables on context > + * switches between themselves. > + * > + * The VM id should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. > + * > + * On GPUs with graphics version 12 and earlier, it may also be set via > + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for > + * backwards compatibility with old userspace and should be considered > + * deprecated. Starting with graphics version 13, it can only be set via > + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be > + * set once for each context and, once the context has been used with any > + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. > + * > + * See DRM_I915_GEM_VM_CREATE and DRM_I915_GEM_VM_DESTROY. Again for kerneldoc linking to the struct of the ioctl is probably better, since then you get a link. > + */ > #define I915_CONTEXT_PARAM_VM 0x9 > > /* > @@ -1700,8 +1710,15 @@ struct drm_i915_gem_context_param { > * to specify a gap in the array that can be filled in later, e.g. by a > * virtual engine used for load balancing. > * > - * Setting the number of engines bound to the context to 0, by passing a zero > - * sized argument, will revert back to default settings. > + * The engine set should only be set via I915_CONTEXT_CREATE_EXT_SETPARAM. > + * > + * On GPUs with graphics version 12 and earlier, it may also be set via > + * DRM_IOCTL_I915_GEM_CONTEXT_SETPARAM. However, this is only for > + * backwards compatibility with old userspace and should be considered > + * deprecated. Starting with graphics version 13, it can only be set via > + * I915_CONTEXT_CREATE_EXT_SETPARAM. When using setparam, it may only be > + * set once for each context and, once the context has been used with any > + * ioctl other than I915_CONTEXT_CREATE_EXT_SETPARAM, it may not be set. > * > * See struct i915_context_param_engines. Maybe we should push most of the docs for params with structs into the struct's kerneldoc? -Daniel > * > -- > 2.31.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Better document VM and engine set APIs 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand ` (2 preceding siblings ...) (?) @ 2021-07-10 22:05 ` Patchwork -1 siblings, 0 replies; 13+ messages in thread From: Patchwork @ 2021-07-10 22:05 UTC (permalink / raw) To: Jason Ekstrand; +Cc: intel-gfx == Series Details == Series: drm/i915: Better document VM and engine set APIs URL : https://patchwork.freedesktop.org/series/92403/ State : warning == Summary == $ dim checkpatch origin/drm-tip 7e293cab2b16 drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice bb17bb50227a drm/i915/uapi: Add docs about immutability of engine sets and VMs -:8: WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one total: 0 errors, 1 warnings, 0 checks, 51 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Better document VM and engine set APIs 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand ` (3 preceding siblings ...) (?) @ 2021-07-10 22:32 ` Patchwork -1 siblings, 0 replies; 13+ messages in thread From: Patchwork @ 2021-07-10 22:32 UTC (permalink / raw) To: Jason Ekstrand; +Cc: intel-gfx [-- Attachment #1.1: Type: text/plain, Size: 2510 bytes --] == Series Details == Series: drm/i915: Better document VM and engine set APIs URL : https://patchwork.freedesktop.org/series/92403/ State : success == Summary == CI Bug Log - changes from CI_DRM_10330 -> Patchwork_20569 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/index.html Known issues ------------ Here are the changes found in Patchwork_20569 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_suspend@basic-s0: - fi-cfl-8109u: [PASS][1] -> [INCOMPLETE][2] ([i915#155]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/fi-cfl-8109u/igt@gem_exec_suspend@basic-s0.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/fi-cfl-8109u/igt@gem_exec_suspend@basic-s0.html #### Possible fixes #### * igt@kms_chamelium@dp-crc-fast: - fi-kbl-7500u: [FAIL][3] ([i915#1372]) -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/fi-kbl-7500u/igt@kms_chamelium@dp-crc-fast.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372 [i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155 [i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888 Participating hosts (41 -> 39) ------------------------------ Missing (2): fi-bsw-cyan fi-bdw-samus Build changes ------------- * IGT: IGT_6134 -> IGTPW_6011 * Linux: CI_DRM_10330 -> Patchwork_20569 CI-20190529: 20190529 CI_DRM_10330: 4d00e2309398147acdbfefbe1deb4b0e78868466 @ git://anongit.freedesktop.org/gfx-ci/linux IGTPW_6011: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6011/index.html IGT_6134: cd63c83e23789eb194d38b8d272247a88122f2f6 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_20569: bb17bb50227a3af5edb3b02f2e6318b8d4728078 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == bb17bb50227a drm/i915/uapi: Add docs about immutability of engine sets and VMs 7e293cab2b16 drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/index.html [-- Attachment #1.2: Type: text/html, Size: 3091 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Better document VM and engine set APIs 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand ` (4 preceding siblings ...) (?) @ 2021-07-11 0:10 ` Patchwork -1 siblings, 0 replies; 13+ messages in thread From: Patchwork @ 2021-07-11 0:10 UTC (permalink / raw) To: Jason Ekstrand; +Cc: intel-gfx [-- Attachment #1.1: Type: text/plain, Size: 30271 bytes --] == Series Details == Series: drm/i915: Better document VM and engine set APIs URL : https://patchwork.freedesktop.org/series/92403/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10330_full -> Patchwork_20569_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_20569_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20569_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_20569_full: ### IGT changes ### #### Possible regressions #### * igt@kms_flip@flip-vs-suspend-interruptible@c-edp1: - shard-iclb: [PASS][1] -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-iclb1/igt@kms_flip@flip-vs-suspend-interruptible@c-edp1.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@kms_flip@flip-vs-suspend-interruptible@c-edp1.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs: - {shard-rkl}: [FAIL][3] ([i915#3678]) -> [SKIP][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-rkl-1/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-rkl-6/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html * igt@kms_flip_tiling@flip-changes-tiling-y: - {shard-rkl}: NOTRUN -> [SKIP][5] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-rkl-1/igt@kms_flip_tiling@flip-changes-tiling-y.html Known issues ------------ Here are the changes found in Patchwork_20569_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@feature_discovery@display-4x: - shard-tglb: NOTRUN -> [SKIP][6] ([i915#1839]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@feature_discovery@display-4x.html - shard-iclb: NOTRUN -> [SKIP][7] ([i915#1839]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@feature_discovery@display-4x.html * igt@gem_create@create-massive: - shard-iclb: NOTRUN -> [DMESG-WARN][8] ([i915#3002]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb4/igt@gem_create@create-massive.html - shard-snb: NOTRUN -> [DMESG-WARN][9] ([i915#3002]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-snb6/igt@gem_create@create-massive.html - shard-kbl: NOTRUN -> [DMESG-WARN][10] ([i915#3002]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl3/igt@gem_create@create-massive.html - shard-tglb: NOTRUN -> [DMESG-WARN][11] ([i915#3002]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb6/igt@gem_create@create-massive.html - shard-glk: NOTRUN -> [DMESG-WARN][12] ([i915#3002]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk3/igt@gem_create@create-massive.html - shard-skl: NOTRUN -> [DMESG-WARN][13] ([i915#3002]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl2/igt@gem_create@create-massive.html - shard-apl: NOTRUN -> [DMESG-WARN][14] ([i915#3002]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl8/igt@gem_create@create-massive.html * igt@gem_ctx_persistence@legacy-engines-hostile-preempt: - shard-snb: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#1099]) +2 similar issues [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-snb5/igt@gem_ctx_persistence@legacy-engines-hostile-preempt.html * igt@gem_exec_fair@basic-none-share@rcs0: - shard-iclb: NOTRUN -> [FAIL][16] ([i915#2842]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb8/igt@gem_exec_fair@basic-none-share@rcs0.html * igt@gem_exec_fair@basic-pace-share@rcs0: - shard-tglb: [PASS][17] -> [FAIL][18] ([i915#2842]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@gem_exec_fair@basic-pace@bcs0: - shard-iclb: [PASS][19] -> [FAIL][20] ([i915#2842]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-iclb4/igt@gem_exec_fair@basic-pace@bcs0.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@gem_exec_fair@basic-pace@bcs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-glk: [PASS][21] -> [FAIL][22] ([i915#2842]) +2 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-glk9/igt@gem_exec_fair@basic-throttle@rcs0.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk4/igt@gem_exec_fair@basic-throttle@rcs0.html - shard-iclb: [PASS][23] -> [FAIL][24] ([i915#2849]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-iclb7/igt@gem_exec_fair@basic-throttle@rcs0.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb5/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_exec_whisper@basic-contexts-forked-all: - shard-glk: [PASS][25] -> [DMESG-WARN][26] ([i915#118] / [i915#95]) [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-glk9/igt@gem_exec_whisper@basic-contexts-forked-all.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk6/igt@gem_exec_whisper@basic-contexts-forked-all.html * igt@gem_mmap_gtt@big-copy: - shard-glk: [PASS][27] -> [FAIL][28] ([i915#307]) +1 similar issue [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-glk3/igt@gem_mmap_gtt@big-copy.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk2/igt@gem_mmap_gtt@big-copy.html * igt@gem_mmap_gtt@big-copy-xy: - shard-iclb: NOTRUN -> [FAIL][29] ([i915#307]) [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@gem_mmap_gtt@big-copy-xy.html - shard-glk: NOTRUN -> [FAIL][30] ([i915#307]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk2/igt@gem_mmap_gtt@big-copy-xy.html * igt@gem_mmap_gtt@coherency: - shard-tglb: NOTRUN -> [SKIP][31] ([fdo#111656]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb1/igt@gem_mmap_gtt@coherency.html - shard-iclb: NOTRUN -> [SKIP][32] ([fdo#109292]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb6/igt@gem_mmap_gtt@coherency.html * igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled: - shard-iclb: NOTRUN -> [SKIP][33] ([i915#768]) [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled.html * igt@gem_userptr_blits@dmabuf-sync: - shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#3323]) [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl1/igt@gem_userptr_blits@dmabuf-sync.html - shard-skl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3323]) [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl3/igt@gem_userptr_blits@dmabuf-sync.html * igt@gem_userptr_blits@readonly-pwrite-unsync: - shard-tglb: NOTRUN -> [SKIP][36] ([i915#3297]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb2/igt@gem_userptr_blits@readonly-pwrite-unsync.html - shard-iclb: NOTRUN -> [SKIP][37] ([i915#3297]) +1 similar issue [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@gem_userptr_blits@readonly-pwrite-unsync.html * igt@gem_userptr_blits@vma-merge: - shard-skl: NOTRUN -> [FAIL][38] ([i915#3318]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl2/igt@gem_userptr_blits@vma-merge.html * igt@gen3_render_linear_blits: - shard-iclb: NOTRUN -> [SKIP][39] ([fdo#109289]) +3 similar issues [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb7/igt@gen3_render_linear_blits.html * igt@gen3_render_tiledy_blits: - shard-tglb: NOTRUN -> [SKIP][40] ([fdo#109289]) +2 similar issues [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb7/igt@gen3_render_tiledy_blits.html * igt@gen9_exec_parse@basic-rejected: - shard-iclb: NOTRUN -> [SKIP][41] ([fdo#112306]) +2 similar issues [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@gen9_exec_parse@basic-rejected.html * igt@gen9_exec_parse@cmd-crossing-page: - shard-tglb: NOTRUN -> [SKIP][42] ([fdo#112306]) +3 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@gen9_exec_parse@cmd-crossing-page.html * igt@i915_pm_dc@dc6-dpms: - shard-kbl: NOTRUN -> [FAIL][43] ([i915#454]) [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl7/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@modeset-non-lpsp-stress: - shard-tglb: NOTRUN -> [SKIP][44] ([fdo#111644] / [i915#1397] / [i915#2411]) [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb2/igt@i915_pm_rpm@modeset-non-lpsp-stress.html - shard-iclb: NOTRUN -> [SKIP][45] ([fdo#110892]) [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@i915_pm_rpm@modeset-non-lpsp-stress.html * igt@i915_pm_rpm@system-suspend-modeset: - shard-kbl: NOTRUN -> [INCOMPLETE][46] ([i915#151] / [i915#155]) [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl2/igt@i915_pm_rpm@system-suspend-modeset.html * igt@i915_selftest@live@gt_pm: - shard-skl: NOTRUN -> [DMESG-FAIL][47] ([i915#1886] / [i915#2291]) [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl8/igt@i915_selftest@live@gt_pm.html * igt@i915_suspend@debugfs-reader: - shard-kbl: NOTRUN -> [DMESG-WARN][48] ([i915#180]) [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl7/igt@i915_suspend@debugfs-reader.html * igt@kms_async_flips@alternate-sync-async-flip: - shard-skl: NOTRUN -> [FAIL][49] ([i915#2521]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl4/igt@kms_async_flips@alternate-sync-async-flip.html * igt@kms_atomic_transition@plane-all-modeset-transition: - shard-iclb: NOTRUN -> [SKIP][50] ([i915#1769]) [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@kms_atomic_transition@plane-all-modeset-transition.html - shard-tglb: NOTRUN -> [SKIP][51] ([i915#1769]) [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@kms_atomic_transition@plane-all-modeset-transition.html * igt@kms_atomic_transition@plane-toggle-modeset-transition: - shard-skl: [PASS][52] -> [SKIP][53] ([fdo#109271]) +11 similar issues [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl10/igt@kms_atomic_transition@plane-toggle-modeset-transition.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_atomic_transition@plane-toggle-modeset-transition.html * igt@kms_big_fb@linear-16bpp-rotate-90: - shard-iclb: NOTRUN -> [SKIP][54] ([fdo#110725] / [fdo#111614]) [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@kms_big_fb@linear-16bpp-rotate-90.html - shard-tglb: NOTRUN -> [SKIP][55] ([fdo#111614]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@kms_big_fb@linear-16bpp-rotate-90.html * igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip: - shard-skl: NOTRUN -> [FAIL][56] ([i915#3763]) +1 similar issue [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl7/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip.html * igt@kms_big_fb@yf-tiled-64bpp-rotate-270: - shard-tglb: NOTRUN -> [SKIP][57] ([fdo#111615]) +4 similar issues [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb2/igt@kms_big_fb@yf-tiled-64bpp-rotate-270.html * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip: - shard-skl: NOTRUN -> [FAIL][58] ([i915#3722]) +1 similar issue [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl8/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html * igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0: - shard-apl: NOTRUN -> [SKIP][59] ([fdo#109271]) +246 similar issues [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl1/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0.html * igt@kms_big_joiner@2x-modeset: - shard-tglb: NOTRUN -> [SKIP][60] ([i915#2705]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb3/igt@kms_big_joiner@2x-modeset.html * igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs: - shard-tglb: NOTRUN -> [SKIP][61] ([i915#3689]) +12 similar issues [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb1/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs: - shard-skl: [PASS][62] -> [FAIL][63] ([i915#3678]) [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl1/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html * igt@kms_ccs@pipe-d-bad-rotation-90-y_tiled_gen12_rc_ccs: - shard-skl: NOTRUN -> [FAIL][64] ([i915#3678]) +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_ccs@pipe-d-bad-rotation-90-y_tiled_gen12_rc_ccs.html * igt@kms_chamelium@hdmi-crc-nonplanar-formats: - shard-glk: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +11 similar issues [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk2/igt@kms_chamelium@hdmi-crc-nonplanar-formats.html * igt@kms_chamelium@hdmi-hpd-enable-disable-mode: - shard-snb: NOTRUN -> [SKIP][66] ([fdo#109271] / [fdo#111827]) +24 similar issues [66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-snb5/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html * igt@kms_chamelium@hdmi-hpd-storm: - shard-kbl: NOTRUN -> [SKIP][67] ([fdo#109271] / [fdo#111827]) +18 similar issues [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl1/igt@kms_chamelium@hdmi-hpd-storm.html * igt@kms_chamelium@hdmi-hpd-storm-disable: - shard-skl: NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111827]) +20 similar issues [68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl2/igt@kms_chamelium@hdmi-hpd-storm-disable.html * igt@kms_chamelium@vga-hpd: - shard-apl: NOTRUN -> [SKIP][69] ([fdo#109271] / [fdo#111827]) +23 similar issues [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl6/igt@kms_chamelium@vga-hpd.html * igt@kms_color_chamelium@pipe-a-ctm-red-to-blue: - shard-iclb: NOTRUN -> [SKIP][70] ([fdo#109284] / [fdo#111827]) +8 similar issues [70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb4/igt@kms_color_chamelium@pipe-a-ctm-red-to-blue.html * igt@kms_color_chamelium@pipe-b-ctm-0-75: - shard-tglb: NOTRUN -> [SKIP][71] ([fdo#109284] / [fdo#111827]) +12 similar issues [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb6/igt@kms_color_chamelium@pipe-b-ctm-0-75.html * igt@kms_color_chamelium@pipe-d-ctm-blue-to-red: - shard-iclb: NOTRUN -> [SKIP][72] ([fdo#109278] / [fdo#109284] / [fdo#111827]) [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@kms_color_chamelium@pipe-d-ctm-blue-to-red.html * igt@kms_content_protection@atomic: - shard-kbl: NOTRUN -> [TIMEOUT][73] ([i915#1319]) +1 similar issue [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl1/igt@kms_content_protection@atomic.html * igt@kms_content_protection@atomic-dpms: - shard-apl: NOTRUN -> [TIMEOUT][74] ([i915#1319]) +1 similar issue [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl1/igt@kms_content_protection@atomic-dpms.html * igt@kms_content_protection@content_type_change: - shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109300] / [fdo#111066]) +2 similar issues [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb4/igt@kms_content_protection@content_type_change.html - shard-tglb: NOTRUN -> [SKIP][76] ([fdo#111828]) +2 similar issues [76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb7/igt@kms_content_protection@content_type_change.html * igt@kms_cursor_crc@pipe-a-cursor-32x32-onscreen: - shard-tglb: NOTRUN -> [SKIP][77] ([i915#3319]) [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-32x32-onscreen.html * igt@kms_cursor_crc@pipe-a-cursor-dpms: - shard-glk: [PASS][78] -> [FAIL][79] ([i915#3444]) [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-glk7/igt@kms_cursor_crc@pipe-a-cursor-dpms.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk1/igt@kms_cursor_crc@pipe-a-cursor-dpms.html - shard-skl: [PASS][80] -> [FAIL][81] ([i915#3444]) [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl7/igt@kms_cursor_crc@pipe-a-cursor-dpms.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl8/igt@kms_cursor_crc@pipe-a-cursor-dpms.html - shard-apl: [PASS][82] -> [FAIL][83] ([i915#3444]) [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-apl2/igt@kms_cursor_crc@pipe-a-cursor-dpms.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl6/igt@kms_cursor_crc@pipe-a-cursor-dpms.html * igt@kms_cursor_crc@pipe-c-cursor-32x10-rapid-movement: - shard-tglb: NOTRUN -> [SKIP][84] ([i915#3359]) +4 similar issues [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb2/igt@kms_cursor_crc@pipe-c-cursor-32x10-rapid-movement.html * igt@kms_cursor_crc@pipe-c-cursor-512x170-random: - shard-iclb: NOTRUN -> [SKIP][85] ([fdo#109278] / [fdo#109279]) +2 similar issues [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@kms_cursor_crc@pipe-c-cursor-512x170-random.html * igt@kms_cursor_crc@pipe-c-cursor-512x512-random: - shard-tglb: NOTRUN -> [SKIP][86] ([fdo#109279] / [i915#3359]) +5 similar issues [86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb3/igt@kms_cursor_crc@pipe-c-cursor-512x512-random.html * igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen: - shard-kbl: NOTRUN -> [SKIP][87] ([fdo#109271]) +218 similar issues [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl2/igt@kms_cursor_crc@pipe-d-cursor-256x256-onscreen.html * igt@kms_cursor_crc@pipe-d-cursor-32x10-offscreen: - shard-iclb: NOTRUN -> [SKIP][88] ([fdo#109278]) +26 similar issues [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@kms_cursor_crc@pipe-d-cursor-32x10-offscreen.html * igt@kms_cursor_edge_walk@pipe-b-256x256-left-edge: - shard-skl: NOTRUN -> [SKIP][89] ([fdo#109271]) +207 similar issues [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_cursor_edge_walk@pipe-b-256x256-left-edge.html * igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic: - shard-iclb: NOTRUN -> [SKIP][90] ([fdo#109274] / [fdo#109278]) +2 similar issues [90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic.html * igt@kms_cursor_legacy@pipe-d-torture-bo: - shard-kbl: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#533]) [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl1/igt@kms_cursor_legacy@pipe-d-torture-bo.html - shard-apl: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#533]) +1 similar issue [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl6/igt@kms_cursor_legacy@pipe-d-torture-bo.html * igt@kms_dp_tiled_display@basic-test-pattern: - shard-iclb: NOTRUN -> [SKIP][93] ([i915#426]) [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@kms_dp_tiled_display@basic-test-pattern.html - shard-tglb: NOTRUN -> [SKIP][94] ([i915#426]) [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb7/igt@kms_dp_tiled_display@basic-test-pattern.html * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2: - shard-glk: [PASS][95] -> [FAIL][96] ([i915#79]) [95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2.html [96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2.html * igt@kms_flip@2x-plain-flip-ts-check: - shard-tglb: NOTRUN -> [SKIP][97] ([fdo#111825]) +36 similar issues [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb7/igt@kms_flip@2x-plain-flip-ts-check.html * igt@kms_flip@blocking-wf_vblank@a-edp1: - shard-skl: [PASS][98] -> [FAIL][99] ([i915#2122]) +2 similar issues [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl6/igt@kms_flip@blocking-wf_vblank@a-edp1.html [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl6/igt@kms_flip@blocking-wf_vblank@a-edp1.html * igt@kms_flip@flip-vs-expired-vblank@b-edp1: - shard-skl: [PASS][100] -> [FAIL][101] ([i915#79]) [100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl7/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_flip@flip-vs-expired-vblank@b-edp1.html * igt@kms_flip@flip-vs-suspend-interruptible@c-dp1: - shard-apl: NOTRUN -> [DMESG-WARN][102] ([i915#180]) +1 similar issue [102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs: - shard-kbl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#2672]) [103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt: - shard-iclb: NOTRUN -> [SKIP][104] ([fdo#109280]) +22 similar issues [104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-mmap-cpu: - shard-skl: NOTRUN -> [FAIL][105] ([i915#49]) [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl8/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-mmap-cpu.html * igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt: - shard-skl: [PASS][106] -> [FAIL][107] ([i915#49]) [106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl6/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt.html [107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl2/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt.html * igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu: - shard-glk: NOTRUN -> [SKIP][108] ([fdo#109271]) +117 similar issues [108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk3/igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu.html * igt@kms_hdr@bpc-switch-suspend: - shard-skl: [PASS][109] -> [FAIL][110] ([i915#1188]) [109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-skl3/igt@kms_hdr@bpc-switch-suspend.html [110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl2/igt@kms_hdr@bpc-switch-suspend.html * igt@kms_hdr@static-toggle-suspend: - shard-tglb: NOTRUN -> [SKIP][111] ([i915#1187]) [111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb1/igt@kms_hdr@static-toggle-suspend.html * igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb: - shard-apl: NOTRUN -> [FAIL][112] ([i915#265]) [112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl3/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html - shard-kbl: NOTRUN -> [FAIL][113] ([i915#265]) [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl1/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: - shard-skl: NOTRUN -> [FAIL][114] ([fdo#108145] / [i915#265]) +1 similar issue [114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html * igt@kms_plane_alpha_blend@pipe-c-alpha-7efc: - shard-kbl: NOTRUN -> [FAIL][115] ([fdo#108145] / [i915#265]) [115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl2/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html - shard-apl: NOTRUN -> [FAIL][116] ([fdo#108145] / [i915#265]) [116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl6/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html * igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb: - shard-glk: NOTRUN -> [FAIL][117] ([i915#265]) [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk1/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html * igt@kms_plane_lowres@pipe-c-tiling-yf: - shard-tglb: NOTRUN -> [SKIP][118] ([fdo#112054]) [118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb1/igt@kms_plane_lowres@pipe-c-tiling-yf.html * igt@kms_plane_lowres@pipe-d-tiling-y: - shard-tglb: NOTRUN -> [SKIP][119] ([i915#3536]) +1 similar issue [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@kms_plane_lowres@pipe-d-tiling-y.html * igt@kms_plane_scaling@2x-scaler-multi-pipe: - shard-iclb: NOTRUN -> [SKIP][120] ([fdo#109274]) +3 similar issues [120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb1/igt@kms_plane_scaling@2x-scaler-multi-pipe.html * igt@kms_psr2_sf@cursor-plane-update-sf: - shard-tglb: NOTRUN -> [SKIP][121] ([i915#2920]) +3 similar issues [121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb3/igt@kms_psr2_sf@cursor-plane-update-sf.html - shard-skl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#658]) +4 similar issues [122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-skl1/igt@kms_psr2_sf@cursor-plane-update-sf.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1: - shard-iclb: NOTRUN -> [SKIP][123] ([i915#658]) +1 similar issue [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3: - shard-kbl: NOTRUN -> [SKIP][124] ([fdo#109271] / [i915#658]) +5 similar issues [124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-kbl3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html - shard-iclb: NOTRUN -> [SKIP][125] ([i915#2920]) [125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4: - shard-glk: NOTRUN -> [SKIP][126] ([fdo#109271] / [i915#658]) +3 similar issues [126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-glk8/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4.html * igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1: - shard-apl: NOTRUN -> [SKIP][127] ([fdo#109271] / [i915#658]) +4 similar issues [127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-apl2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-1.html * igt@kms_psr2_su@page_flip: - shard-tglb: NOTRUN -> [SKIP][128] ([i915#1911]) [128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-tglb5/igt@kms_psr2_su@page_flip.html * igt@kms_psr@psr2_primary_mmap_cpu: - shard-iclb: NOTRUN -> [SKIP][129] ([fdo#109441]) +2 similar issues [129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html * igt@kms_psr@psr2_sprite_plane_move: - shard-iclb: [PASS][130] -> [SKIP][131] ([fdo#109441]) +1 similar issue [130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10330/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html [131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/shard-iclb3/igt@ == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20569/index.html [-- Attachment #1.2: Type: text/html, Size: 33822 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2021-07-12 14:34 UTC | newest] Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-07-10 21:24 [PATCH 0/2] drm/i915: Better document VM and engine set APIs Jason Ekstrand 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand 2021-07-10 21:24 ` [PATCH 1/2] drm/i915: Don't allow setting I915_CONTEXT_PARAM_VM twice Jason Ekstrand 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand 2021-07-12 14:30 ` Daniel Vetter 2021-07-12 14:30 ` [Intel-gfx] " Daniel Vetter 2021-07-10 21:24 ` [PATCH 2/2] drm/i915/uapi: Add docs about immutability of engine sets and VMs Jason Ekstrand 2021-07-10 21:24 ` [Intel-gfx] " Jason Ekstrand 2021-07-12 14:34 ` Daniel Vetter 2021-07-12 14:34 ` [Intel-gfx] " Daniel Vetter 2021-07-10 22:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Better document VM and engine set APIs Patchwork 2021-07-10 22:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-07-11 0:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.