* [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 15:21 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 15:21 UTC (permalink / raw)
To: intel-gfx
Since retirement may be running in a worker on another CPU, it may be
skipped in the local intel_gt_wait_for_idle(). To ensure the state is
consistent for our sanity checks upon load, serialise with the remote
retirer by waiting on the timeline->mutex.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_gem.c | 26 +++++++++++++++++++++++---
1 file changed, 23 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 1ba5f26700b0..61395b03443e 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -45,6 +45,7 @@
#include "gem/i915_gem_context.h"
#include "gem/i915_gem_ioctls.h"
#include "gem/i915_gem_pm.h"
+#include "gt/intel_context.h"
#include "gt/intel_engine_user.h"
#include "gt/intel_gt.h"
#include "gt/intel_gt_pm.h"
@@ -1041,6 +1042,18 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,
return err;
}
+static int __intel_context_flush_retire(struct intel_context *ce)
+{
+ struct intel_timeline *tl;
+
+ tl = intel_context_timeline_lock(ce);
+ if (IS_ERR(tl))
+ return PTR_ERR(tl);
+
+ intel_context_timeline_unlock(tl);
+ return 0;
+}
+
static int __intel_engines_record_defaults(struct intel_gt *gt)
{
struct i915_request *requests[I915_NUM_ENGINES] = {};
@@ -1109,13 +1122,20 @@ static int __intel_engines_record_defaults(struct intel_gt *gt)
if (!rq)
continue;
- /* We want to be able to unbind the state from the GGTT */
- GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
-
+ GEM_BUG_ON(!test_bit(CONTEXT_ALLOC_BIT,
+ &rq->hw_context->flags));
state = rq->hw_context->state;
if (!state)
continue;
+ /* Serialise with retirement on another CPU */
+ err = __intel_context_flush_retire(rq->hw_context);
+ if (err)
+ goto out;
+
+ /* We want to be able to unbind the state from the GGTT */
+ GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
+
/*
* As we will hold a reference to the logical state, it will
* not be torn down with the context, and importantly the
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [Intel-gfx] [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 15:21 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 15:21 UTC (permalink / raw)
To: intel-gfx
Since retirement may be running in a worker on another CPU, it may be
skipped in the local intel_gt_wait_for_idle(). To ensure the state is
consistent for our sanity checks upon load, serialise with the remote
retirer by waiting on the timeline->mutex.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_gem.c | 26 +++++++++++++++++++++++---
1 file changed, 23 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 1ba5f26700b0..61395b03443e 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -45,6 +45,7 @@
#include "gem/i915_gem_context.h"
#include "gem/i915_gem_ioctls.h"
#include "gem/i915_gem_pm.h"
+#include "gt/intel_context.h"
#include "gt/intel_engine_user.h"
#include "gt/intel_gt.h"
#include "gt/intel_gt_pm.h"
@@ -1041,6 +1042,18 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,
return err;
}
+static int __intel_context_flush_retire(struct intel_context *ce)
+{
+ struct intel_timeline *tl;
+
+ tl = intel_context_timeline_lock(ce);
+ if (IS_ERR(tl))
+ return PTR_ERR(tl);
+
+ intel_context_timeline_unlock(tl);
+ return 0;
+}
+
static int __intel_engines_record_defaults(struct intel_gt *gt)
{
struct i915_request *requests[I915_NUM_ENGINES] = {};
@@ -1109,13 +1122,20 @@ static int __intel_engines_record_defaults(struct intel_gt *gt)
if (!rq)
continue;
- /* We want to be able to unbind the state from the GGTT */
- GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
-
+ GEM_BUG_ON(!test_bit(CONTEXT_ALLOC_BIT,
+ &rq->hw_context->flags));
state = rq->hw_context->state;
if (!state)
continue;
+ /* Serialise with retirement on another CPU */
+ err = __intel_context_flush_retire(rq->hw_context);
+ if (err)
+ goto out;
+
+ /* We want to be able to unbind the state from the GGTT */
+ GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
+
/*
* As we will hold a reference to the logical state, it will
* not be torn down with the context, and importantly the
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 15:21 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 15:21 UTC (permalink / raw)
To: intel-gfx
Before we remove from the timeline, finish flushing the context state.
As the timeline may be peeked upon by another CPU, we don't want to
remove request from the timeline until we have finished working on it.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_request.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
index 00011f9533b6..2445a0693287 100644
--- a/drivers/gpu/drm/i915/i915_request.c
+++ b/drivers/gpu/drm/i915/i915_request.c
@@ -269,12 +269,13 @@ bool i915_request_retire(struct i915_request *rq)
GEM_BUG_ON(!list_empty(&rq->execute_cb));
spin_unlock_irq(&rq->lock);
- remove_from_client(rq);
- list_del(&rq->link);
-
intel_context_exit(rq->hw_context);
intel_context_unpin(rq->hw_context);
+ /* And finally after flushing the state, remove from prying eyes. */
+ remove_from_client(rq);
+ list_del(&rq->link);
+
free_capture_list(rq);
i915_sched_node_fini(&rq->sched);
i915_request_put(rq);
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [Intel-gfx] [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 15:21 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 15:21 UTC (permalink / raw)
To: intel-gfx
Before we remove from the timeline, finish flushing the context state.
As the timeline may be peeked upon by another CPU, we don't want to
remove request from the timeline until we have finished working on it.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_request.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
index 00011f9533b6..2445a0693287 100644
--- a/drivers/gpu/drm/i915/i915_request.c
+++ b/drivers/gpu/drm/i915/i915_request.c
@@ -269,12 +269,13 @@ bool i915_request_retire(struct i915_request *rq)
GEM_BUG_ON(!list_empty(&rq->execute_cb));
spin_unlock_irq(&rq->lock);
- remove_from_client(rq);
- list_del(&rq->link);
-
intel_context_exit(rq->hw_context);
intel_context_unpin(rq->hw_context);
+ /* And finally after flushing the state, remove from prying eyes. */
+ remove_from_client(rq);
+ list_del(&rq->link);
+
free_capture_list(rq);
i915_sched_node_fini(&rq->sched);
i915_request_put(rq);
--
2.24.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 16:05 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:05 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 15:21, Chris Wilson wrote:
> Since retirement may be running in a worker on another CPU, it may be
> skipped in the local intel_gt_wait_for_idle(). To ensure the state is
> consistent for our sanity checks upon load, serialise with the remote
> retirer by waiting on the timeline->mutex.
What may get skipped? Timeline might have been removed from the active
list before wait_for_idle? But why would that be bad for this code? It
just splits part of the retirement to two paths - wait_for_idle still...
oops wait.. indeed.. wait_for_idle used to guarantee retirement and now
it can be ongoing. Does wait_for_idle needs to always wait or you think
case-by-case basis is better?
Regards,
Tvrtko
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 1ba5f26700b0..61395b03443e 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -45,6 +45,7 @@
> #include "gem/i915_gem_context.h"
> #include "gem/i915_gem_ioctls.h"
> #include "gem/i915_gem_pm.h"
> +#include "gt/intel_context.h"
> #include "gt/intel_engine_user.h"
> #include "gt/intel_gt.h"
> #include "gt/intel_gt_pm.h"
> @@ -1041,6 +1042,18 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,
> return err;
> }
>
> +static int __intel_context_flush_retire(struct intel_context *ce)
> +{
> + struct intel_timeline *tl;
> +
> + tl = intel_context_timeline_lock(ce);
> + if (IS_ERR(tl))
> + return PTR_ERR(tl);
> +
> + intel_context_timeline_unlock(tl);
> + return 0;
> +}
> +
> static int __intel_engines_record_defaults(struct intel_gt *gt)
> {
> struct i915_request *requests[I915_NUM_ENGINES] = {};
> @@ -1109,13 +1122,20 @@ static int __intel_engines_record_defaults(struct intel_gt *gt)
> if (!rq)
> continue;
>
> - /* We want to be able to unbind the state from the GGTT */
> - GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
> -
> + GEM_BUG_ON(!test_bit(CONTEXT_ALLOC_BIT,
> + &rq->hw_context->flags));
> state = rq->hw_context->state;
> if (!state)
> continue;
>
> + /* Serialise with retirement on another CPU */
> + err = __intel_context_flush_retire(rq->hw_context);
> + if (err)
> + goto out;
> +
> + /* We want to be able to unbind the state from the GGTT */
> + GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
> +
> /*
> * As we will hold a reference to the logical state, it will
> * not be torn down with the context, and importantly the
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 16:05 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:05 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 15:21, Chris Wilson wrote:
> Since retirement may be running in a worker on another CPU, it may be
> skipped in the local intel_gt_wait_for_idle(). To ensure the state is
> consistent for our sanity checks upon load, serialise with the remote
> retirer by waiting on the timeline->mutex.
What may get skipped? Timeline might have been removed from the active
list before wait_for_idle? But why would that be bad for this code? It
just splits part of the retirement to two paths - wait_for_idle still...
oops wait.. indeed.. wait_for_idle used to guarantee retirement and now
it can be ongoing. Does wait_for_idle needs to always wait or you think
case-by-case basis is better?
Regards,
Tvrtko
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 1ba5f26700b0..61395b03443e 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -45,6 +45,7 @@
> #include "gem/i915_gem_context.h"
> #include "gem/i915_gem_ioctls.h"
> #include "gem/i915_gem_pm.h"
> +#include "gt/intel_context.h"
> #include "gt/intel_engine_user.h"
> #include "gt/intel_gt.h"
> #include "gt/intel_gt_pm.h"
> @@ -1041,6 +1042,18 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,
> return err;
> }
>
> +static int __intel_context_flush_retire(struct intel_context *ce)
> +{
> + struct intel_timeline *tl;
> +
> + tl = intel_context_timeline_lock(ce);
> + if (IS_ERR(tl))
> + return PTR_ERR(tl);
> +
> + intel_context_timeline_unlock(tl);
> + return 0;
> +}
> +
> static int __intel_engines_record_defaults(struct intel_gt *gt)
> {
> struct i915_request *requests[I915_NUM_ENGINES] = {};
> @@ -1109,13 +1122,20 @@ static int __intel_engines_record_defaults(struct intel_gt *gt)
> if (!rq)
> continue;
>
> - /* We want to be able to unbind the state from the GGTT */
> - GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
> -
> + GEM_BUG_ON(!test_bit(CONTEXT_ALLOC_BIT,
> + &rq->hw_context->flags));
> state = rq->hw_context->state;
> if (!state)
> continue;
>
> + /* Serialise with retirement on another CPU */
> + err = __intel_context_flush_retire(rq->hw_context);
> + if (err)
> + goto out;
> +
> + /* We want to be able to unbind the state from the GGTT */
> + GEM_BUG_ON(intel_context_is_pinned(rq->hw_context));
> +
> /*
> * As we will hold a reference to the logical state, it will
> * not be torn down with the context, and importantly the
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:07 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:07 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 15:21, Chris Wilson wrote:
> Before we remove from the timeline, finish flushing the context state.
> As the timeline may be peeked upon by another CPU, we don't want to
> remove request from the timeline until we have finished working on it.
I have to ask why I'm afraid.
Regards,
Tvrtko
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_request.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 00011f9533b6..2445a0693287 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -269,12 +269,13 @@ bool i915_request_retire(struct i915_request *rq)
> GEM_BUG_ON(!list_empty(&rq->execute_cb));
> spin_unlock_irq(&rq->lock);
>
> - remove_from_client(rq);
> - list_del(&rq->link);
> -
> intel_context_exit(rq->hw_context);
> intel_context_unpin(rq->hw_context);
>
> + /* And finally after flushing the state, remove from prying eyes. */
> + remove_from_client(rq);
> + list_del(&rq->link);
> +
> free_capture_list(rq);
> i915_sched_node_fini(&rq->sched);
> i915_request_put(rq);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:07 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:07 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 15:21, Chris Wilson wrote:
> Before we remove from the timeline, finish flushing the context state.
> As the timeline may be peeked upon by another CPU, we don't want to
> remove request from the timeline until we have finished working on it.
I have to ask why I'm afraid.
Regards,
Tvrtko
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_request.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 00011f9533b6..2445a0693287 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -269,12 +269,13 @@ bool i915_request_retire(struct i915_request *rq)
> GEM_BUG_ON(!list_empty(&rq->execute_cb));
> spin_unlock_irq(&rq->lock);
>
> - remove_from_client(rq);
> - list_del(&rq->link);
> -
> intel_context_exit(rq->hw_context);
> intel_context_unpin(rq->hw_context);
>
> + /* And finally after flushing the state, remove from prying eyes. */
> + remove_from_client(rq);
> + list_del(&rq->link);
> +
> free_capture_list(rq);
> i915_sched_node_fini(&rq->sched);
> i915_request_put(rq);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 16:08 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 16:08 UTC (permalink / raw)
To: Tvrtko Ursulin, intel-gfx
Quoting Tvrtko Ursulin (2019-11-20 16:05:24)
>
> On 20/11/2019 15:21, Chris Wilson wrote:
> > Since retirement may be running in a worker on another CPU, it may be
> > skipped in the local intel_gt_wait_for_idle(). To ensure the state is
> > consistent for our sanity checks upon load, serialise with the remote
> > retirer by waiting on the timeline->mutex.
>
> What may get skipped? Timeline might have been removed from the active
> list before wait_for_idle? But why would that be bad for this code? It
> just splits part of the retirement to two paths - wait_for_idle still...
> oops wait.. indeed.. wait_for_idle used to guarantee retirement and now
> it can be ongoing. Does wait_for_idle needs to always wait or you think
> case-by-case basis is better?
My thought was case-by-case, as intel_gt_pm_wait_for_idle() picks up the
slack for when we truly need it. Here, my intent was to avoid waiting
longer than was strictly necessarily.
I probably should have mentioned that as the standby.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 16:08 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 16:08 UTC (permalink / raw)
To: Tvrtko Ursulin, intel-gfx
Quoting Tvrtko Ursulin (2019-11-20 16:05:24)
>
> On 20/11/2019 15:21, Chris Wilson wrote:
> > Since retirement may be running in a worker on another CPU, it may be
> > skipped in the local intel_gt_wait_for_idle(). To ensure the state is
> > consistent for our sanity checks upon load, serialise with the remote
> > retirer by waiting on the timeline->mutex.
>
> What may get skipped? Timeline might have been removed from the active
> list before wait_for_idle? But why would that be bad for this code? It
> just splits part of the retirement to two paths - wait_for_idle still...
> oops wait.. indeed.. wait_for_idle used to guarantee retirement and now
> it can be ongoing. Does wait_for_idle needs to always wait or you think
> case-by-case basis is better?
My thought was case-by-case, as intel_gt_pm_wait_for_idle() picks up the
slack for when we truly need it. Here, my intent was to avoid waiting
longer than was strictly necessarily.
I probably should have mentioned that as the standby.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:12 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 16:12 UTC (permalink / raw)
To: Tvrtko Ursulin, intel-gfx
Quoting Tvrtko Ursulin (2019-11-20 16:07:14)
>
> On 20/11/2019 15:21, Chris Wilson wrote:
> > Before we remove from the timeline, finish flushing the context state.
> > As the timeline may be peeked upon by another CPU, we don't want to
> > remove request from the timeline until we have finished working on it.
>
> I have to ask why I'm afraid.
It's the alternative idea to patch 1. If we reorder the code in the
retire, the sanity checks in patch 1 won't notice the inconsistent
state. I think patch 1 is the better expression: if you are dependent on
seeing the post-retirement state, you should wait until that after
retiring.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:12 ` Chris Wilson
0 siblings, 0 replies; 18+ messages in thread
From: Chris Wilson @ 2019-11-20 16:12 UTC (permalink / raw)
To: Tvrtko Ursulin, intel-gfx
Quoting Tvrtko Ursulin (2019-11-20 16:07:14)
>
> On 20/11/2019 15:21, Chris Wilson wrote:
> > Before we remove from the timeline, finish flushing the context state.
> > As the timeline may be peeked upon by another CPU, we don't want to
> > remove request from the timeline until we have finished working on it.
>
> I have to ask why I'm afraid.
It's the alternative idea to patch 1. If we reorder the code in the
retire, the sanity checks in patch 1 won't notice the inconsistent
state. I think patch 1 is the better expression: if you are dependent on
seeing the post-retirement state, you should wait until that after
retiring.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:16 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:16 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 16:12, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-11-20 16:07:14)
>>
>> On 20/11/2019 15:21, Chris Wilson wrote:
>>> Before we remove from the timeline, finish flushing the context state.
>>> As the timeline may be peeked upon by another CPU, we don't want to
>>> remove request from the timeline until we have finished working on it.
>>
>> I have to ask why I'm afraid.
>
> It's the alternative idea to patch 1. If we reorder the code in the
> retire, the sanity checks in patch 1 won't notice the inconsistent
> state. I think patch 1 is the better expression: if you are dependent on
> seeing the post-retirement state, you should wait until that after
> retiring.
Yes I agree. This patch had me completely puzzled who could relying on
such subtleties.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring
@ 2019-11-20 16:16 ` Tvrtko Ursulin
0 siblings, 0 replies; 18+ messages in thread
From: Tvrtko Ursulin @ 2019-11-20 16:16 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 20/11/2019 16:12, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-11-20 16:07:14)
>>
>> On 20/11/2019 15:21, Chris Wilson wrote:
>>> Before we remove from the timeline, finish flushing the context state.
>>> As the timeline may be peeked upon by another CPU, we don't want to
>>> remove request from the timeline until we have finished working on it.
>>
>> I have to ask why I'm afraid.
>
> It's the alternative idea to patch 1. If we reorder the code in the
> retire, the sanity checks in patch 1 won't notice the inconsistent
> state. I think patch 1 is the better expression: if you are dependent on
> seeing the post-retirement state, you should wait until that after
> retiring.
Yes I agree. This patch had me completely puzzled who could relying on
such subtleties.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 20:50 ` Patchwork
0 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-11-20 20:50 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: series starting with [1/2] drm/i915: Serialise with remote retirement
URL : https://patchwork.freedesktop.org/series/69757/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7390 -> Patchwork_15347
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
Known issues
------------
Here are the changes found in Patchwork_15347 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([fdo#112120])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-bsw-kefka/igt@gem_exec_suspend@basic-s0.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-bsw-kefka/igt@gem_exec_suspend@basic-s0.html
#### Possible fixes ####
* igt@prime_vgem@basic-fence-flip:
- fi-icl-dsi: [DMESG-WARN][3] ([fdo#106107]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-icl-dsi/igt@prime_vgem@basic-fence-flip.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-icl-dsi/igt@prime_vgem@basic-fence-flip.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][5] ([fdo#111045] / [fdo#111096]) -> [FAIL][6] ([fdo#111407])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#109964]: https://bugs.freedesktop.org/show_bug.cgi?id=109964
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880
[fdo#112120]: https://bugs.freedesktop.org/show_bug.cgi?id=112120
[fdo#112298]: https://bugs.freedesktop.org/show_bug.cgi?id=112298
Participating hosts (49 -> 45)
------------------------------
Additional (2): fi-bdw-5557u fi-skl-6600u
Missing (6): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7390 -> Patchwork_15347
CI-20190529: 20190529
CI_DRM_7390: a5c38d3c64698a5cfdb1230d5c3c59e7714746b1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5299: 65fed6a79adea14f7bef6d55530da47d7731d370 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15347: efb2680506ace62b50a99fefdcdf5c46113e2fe0 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
efb2680506ac drm/i915: Remove the timeline as the last step of retiring
1c0da7b688de drm/i915: Serialise with remote retirement
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Serialise with remote retirement
@ 2019-11-20 20:50 ` Patchwork
0 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-11-20 20:50 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: series starting with [1/2] drm/i915: Serialise with remote retirement
URL : https://patchwork.freedesktop.org/series/69757/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7390 -> Patchwork_15347
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
Known issues
------------
Here are the changes found in Patchwork_15347 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s0:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([fdo#112120])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-bsw-kefka/igt@gem_exec_suspend@basic-s0.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-bsw-kefka/igt@gem_exec_suspend@basic-s0.html
#### Possible fixes ####
* igt@prime_vgem@basic-fence-flip:
- fi-icl-dsi: [DMESG-WARN][3] ([fdo#106107]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-icl-dsi/igt@prime_vgem@basic-fence-flip.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-icl-dsi/igt@prime_vgem@basic-fence-flip.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][5] ([fdo#111045] / [fdo#111096]) -> [FAIL][6] ([fdo#111407])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#109964]: https://bugs.freedesktop.org/show_bug.cgi?id=109964
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880
[fdo#112120]: https://bugs.freedesktop.org/show_bug.cgi?id=112120
[fdo#112298]: https://bugs.freedesktop.org/show_bug.cgi?id=112298
Participating hosts (49 -> 45)
------------------------------
Additional (2): fi-bdw-5557u fi-skl-6600u
Missing (6): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7390 -> Patchwork_15347
CI-20190529: 20190529
CI_DRM_7390: a5c38d3c64698a5cfdb1230d5c3c59e7714746b1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5299: 65fed6a79adea14f7bef6d55530da47d7731d370 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15347: efb2680506ace62b50a99fefdcdf5c46113e2fe0 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
efb2680506ac drm/i915: Remove the timeline as the last step of retiring
1c0da7b688de drm/i915: Serialise with remote retirement
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915: Serialise with remote retirement
@ 2019-11-21 17:29 ` Patchwork
0 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-11-21 17:29 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: series starting with [1/2] drm/i915: Serialise with remote retirement
URL : https://patchwork.freedesktop.org/series/69757/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7390_full -> Patchwork_15347_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_15347_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@vcs1-dirty-create:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#109276] / [fdo#112080]) +4 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@gem_ctx_isolation@vcs1-dirty-create.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb3/igt@gem_ctx_isolation@vcs1-dirty-create.html
* igt@gem_eio@in-flight-suspend:
- shard-tglb: [PASS][3] -> [INCOMPLETE][4] ([fdo#111832] / [fdo#111850] / [fdo#112081])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@gem_eio@in-flight-suspend.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_reloc@basic-cpu-active:
- shard-skl: [PASS][5] -> [DMESG-WARN][6] ([fdo#106107])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@gem_exec_reloc@basic-cpu-active.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@gem_exec_reloc@basic-cpu-active.html
* igt@gem_exec_schedule@fifo-bsd1:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276]) +18 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb1/igt@gem_exec_schedule@fifo-bsd1.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb6/igt@gem_exec_schedule@fifo-bsd1.html
* igt@gem_exec_schedule@preempt-bsd:
- shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#112146]) +5 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_exec_schedule@preempt-bsd.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_exec_schedule@preempt-bsd.html
* igt@gem_exec_schedule@preempt-queue-contexts-vebox:
- shard-tglb: [PASS][11] -> [INCOMPLETE][12] ([fdo#111677]) +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb9/igt@gem_exec_schedule@preempt-queue-contexts-vebox.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb6/igt@gem_exec_schedule@preempt-queue-contexts-vebox.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-hsw: [PASS][13] -> [DMESG-WARN][14] ([fdo#111870]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw1/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw8/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
- shard-snb: [PASS][15] -> [DMESG-WARN][16] ([fdo#111870])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@i915_selftest@live_hangcheck:
- shard-hsw: [PASS][17] -> [DMESG-FAIL][18] ([fdo#111991])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw8/igt@i915_selftest@live_hangcheck.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw2/igt@i915_selftest@live_hangcheck.html
* igt@kms_color@pipe-b-ctm-negative:
- shard-skl: [PASS][19] -> [FAIL][20] ([fdo#107361])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@kms_color@pipe-b-ctm-negative.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl1/igt@kms_color@pipe-b-ctm-negative.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-tglb: [PASS][21] -> [INCOMPLETE][22] ([fdo#111832] / [fdo#111850]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([fdo#108566]) +5 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [PASS][25] -> [FAIL][26] ([fdo#105363]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@kms_flip@flip-vs-expired-vblank.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-glk: [PASS][27] -> [FAIL][28] ([fdo#105363])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-glk3/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-glk1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend:
- shard-snb: [PASS][29] -> [INCOMPLETE][30] ([fdo#105411])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb7/igt@kms_flip@flip-vs-suspend.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb1/igt@kms_flip@flip-vs-suspend.html
- shard-hsw: [PASS][31] -> [INCOMPLETE][32] ([fdo#103540])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw4/igt@kms_flip@flip-vs-suspend.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw1/igt@kms_flip@flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [PASS][33] -> [FAIL][34] ([fdo#103167]) +4 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move:
- shard-iclb: [PASS][35] -> [FAIL][36] ([fdo#103167]) +3 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [PASS][37] -> [DMESG-WARN][38] ([fdo#108566]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][39] -> [INCOMPLETE][40] ([fdo#104108]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [PASS][41] -> [FAIL][42] ([fdo#103166])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb2/igt@kms_plane_lowres@pipe-a-tiling-y.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][43] -> [SKIP][44] ([fdo#109441]) +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-kbl: [PASS][45] -> [FAIL][46] ([fdo#99912])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl2/igt@kms_setmode@basic.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl1/igt@kms_setmode@basic.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-tglb: [PASS][47] -> [INCOMPLETE][48] ([fdo#111850])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb4/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
* igt@perf_pmu@busy-check-all-vcs1:
- shard-iclb: [PASS][49] -> [SKIP][50] ([fdo#112080]) +13 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@perf_pmu@busy-check-all-vcs1.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb5/igt@perf_pmu@busy-check-all-vcs1.html
#### Possible fixes ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [SKIP][51] ([fdo#112080]) -> [PASS][52] +16 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@gem_busy@busy-vcs1.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@gem_busy@busy-vcs1.html
* igt@gem_ctx_isolation@vecs0-s3:
- shard-kbl: [DMESG-WARN][53] ([fdo#103313]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl6/igt@gem_ctx_isolation@vecs0-s3.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl7/igt@gem_ctx_isolation@vecs0-s3.html
* igt@gem_ctx_persistence@vcs1-mixed-process:
- shard-iclb: [SKIP][55] ([fdo#109276] / [fdo#112080]) -> [PASS][56] +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@gem_ctx_persistence@vcs1-mixed-process.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@gem_ctx_persistence@vcs1-mixed-process.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][57] ([fdo#110854]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_exec_balancer@smoke.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [SKIP][59] ([fdo#112146]) -> [PASS][60] +10 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb5/igt@gem_exec_schedule@preempt-other-chain-bsd.html
* igt@gem_exec_schedule@preempt-queue-bsd2:
- shard-tglb: [INCOMPLETE][61] ([fdo#111606] / [fdo#111677]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb6/igt@gem_exec_schedule@preempt-queue-bsd2.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb2/igt@gem_exec_schedule@preempt-queue-bsd2.html
* igt@gem_persistent_relocs@forked-interruptible-thrash-inactive:
- shard-snb: [TIMEOUT][63] ([fdo#112068 ]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb2/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb6/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
* igt@gem_sync@basic-store-all:
- shard-tglb: [INCOMPLETE][65] ([fdo#111880]) -> [PASS][66] +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb6/igt@gem_sync@basic-store-all.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb7/igt@gem_sync@basic-store-all.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-hsw: [DMESG-WARN][67] ([fdo#111870]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw5/igt@gem_userptr_blits@sync-unmap-cycles.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw2/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@i915_pm_backlight@fade_with_suspend:
- shard-tglb: [INCOMPLETE][69] ([fdo#111832] / [fdo#111850]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb7/igt@i915_pm_backlight@fade_with_suspend.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@i915_pm_backlight@fade_with_suspend.html
* igt@kms_color@pipe-a-ctm-0-25:
- shard-skl: [DMESG-WARN][71] ([fdo#106107]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl3/igt@kms_color@pipe-a-ctm-0-25.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl2/igt@kms_color@pipe-a-ctm-0-25.html
* igt@kms_cursor_crc@pipe-a-cursor-64x64-random:
- shard-tglb: [INCOMPLETE][73] -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb6/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][75] ([fdo#108566]) -> [PASS][76] +4 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic:
- shard-skl: [FAIL][77] ([fdo#102670]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html
* igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled:
- shard-skl: [FAIL][79] ([fdo#103184] / [fdo#103232] / [fdo#108472]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-tglb: [INCOMPLETE][81] ([fdo#111747] / [fdo#111832] / [fdo#111850]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@kms_fbcon_fbt@fbc-suspend.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb1/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@nonblocking-read:
- shard-kbl: [DMESG-WARN][83] ([fdo#103558] / [fdo#105602]) -> [PASS][84] +8 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl3/igt@kms_flip@nonblocking-read.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl6/igt@kms_flip@nonblocking-read.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-iclb: [FAIL][85] ([fdo#103167]) -> [PASS][86] +4 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt:
- shard-tglb: [FAIL][87] ([fdo#103167]) -> [PASS][88] +3 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: [DMESG-WARN][89] ([fdo#108566]) -> [PASS][90] +3 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-apl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][91] ([fdo#108145] / [fdo#110403]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][93] ([fdo#109441]) -> [PASS][94] +3 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@kms_psr@psr2_sprite_plane_move.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-tglb: [INCOMPLETE][95] ([fdo#111850]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb4/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [SKIP][97] ([fdo#109276]) -> [PASS][98] +20 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb3/igt@prime_vgem@fence-wait-bsd2.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@prime_vgem@fence-wait-bsd2.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [SKIP][99] ([fdo#109276] / [fdo#112080]) -> [FAIL][100] ([fdo#111329]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_ctx_isolation@vcs1-nonpriv.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@i915_pm_dc@dc6-psr:
- shard-skl: [FAIL][101] ([fdo#111830 ]) -> [INCOMPLETE][102] ([fdo#108972])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@i915_pm_dc@dc6-psr.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@i915_pm_dc@dc6-psr.html
[fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103184]: https://bugs.freedesktop.org/show_bug.cgi?id=103184
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103313]: https://bugs.freedesktop.org/show_bug.cgi?id=103313
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: h
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915: Serialise with remote retirement
@ 2019-11-21 17:29 ` Patchwork
0 siblings, 0 replies; 18+ messages in thread
From: Patchwork @ 2019-11-21 17:29 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: series starting with [1/2] drm/i915: Serialise with remote retirement
URL : https://patchwork.freedesktop.org/series/69757/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7390_full -> Patchwork_15347_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_15347_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@vcs1-dirty-create:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#109276] / [fdo#112080]) +4 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@gem_ctx_isolation@vcs1-dirty-create.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb3/igt@gem_ctx_isolation@vcs1-dirty-create.html
* igt@gem_eio@in-flight-suspend:
- shard-tglb: [PASS][3] -> [INCOMPLETE][4] ([fdo#111832] / [fdo#111850] / [fdo#112081])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@gem_eio@in-flight-suspend.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@gem_eio@in-flight-suspend.html
* igt@gem_exec_reloc@basic-cpu-active:
- shard-skl: [PASS][5] -> [DMESG-WARN][6] ([fdo#106107])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@gem_exec_reloc@basic-cpu-active.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@gem_exec_reloc@basic-cpu-active.html
* igt@gem_exec_schedule@fifo-bsd1:
- shard-iclb: [PASS][7] -> [SKIP][8] ([fdo#109276]) +18 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb1/igt@gem_exec_schedule@fifo-bsd1.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb6/igt@gem_exec_schedule@fifo-bsd1.html
* igt@gem_exec_schedule@preempt-bsd:
- shard-iclb: [PASS][9] -> [SKIP][10] ([fdo#112146]) +5 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_exec_schedule@preempt-bsd.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_exec_schedule@preempt-bsd.html
* igt@gem_exec_schedule@preempt-queue-contexts-vebox:
- shard-tglb: [PASS][11] -> [INCOMPLETE][12] ([fdo#111677]) +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb9/igt@gem_exec_schedule@preempt-queue-contexts-vebox.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb6/igt@gem_exec_schedule@preempt-queue-contexts-vebox.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-hsw: [PASS][13] -> [DMESG-WARN][14] ([fdo#111870]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw1/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw8/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
- shard-snb: [PASS][15] -> [DMESG-WARN][16] ([fdo#111870])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@i915_selftest@live_hangcheck:
- shard-hsw: [PASS][17] -> [DMESG-FAIL][18] ([fdo#111991])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw8/igt@i915_selftest@live_hangcheck.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw2/igt@i915_selftest@live_hangcheck.html
* igt@kms_color@pipe-b-ctm-negative:
- shard-skl: [PASS][19] -> [FAIL][20] ([fdo#107361])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@kms_color@pipe-b-ctm-negative.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl1/igt@kms_color@pipe-b-ctm-negative.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-tglb: [PASS][21] -> [INCOMPLETE][22] ([fdo#111832] / [fdo#111850]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb5/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([fdo#108566]) +5 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [PASS][25] -> [FAIL][26] ([fdo#105363]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@kms_flip@flip-vs-expired-vblank.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-glk: [PASS][27] -> [FAIL][28] ([fdo#105363])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-glk3/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-glk1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend:
- shard-snb: [PASS][29] -> [INCOMPLETE][30] ([fdo#105411])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb7/igt@kms_flip@flip-vs-suspend.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb1/igt@kms_flip@flip-vs-suspend.html
- shard-hsw: [PASS][31] -> [INCOMPLETE][32] ([fdo#103540])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw4/igt@kms_flip@flip-vs-suspend.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw1/igt@kms_flip@flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt:
- shard-tglb: [PASS][33] -> [FAIL][34] ([fdo#103167]) +4 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move:
- shard-iclb: [PASS][35] -> [FAIL][36] ([fdo#103167]) +3 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [PASS][37] -> [DMESG-WARN][38] ([fdo#108566]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-apl1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][39] -> [INCOMPLETE][40] ([fdo#104108]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl8/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [PASS][41] -> [FAIL][42] ([fdo#103166])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb2/igt@kms_plane_lowres@pipe-a-tiling-y.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][43] -> [SKIP][44] ([fdo#109441]) +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-kbl: [PASS][45] -> [FAIL][46] ([fdo#99912])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl2/igt@kms_setmode@basic.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl1/igt@kms_setmode@basic.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- shard-tglb: [PASS][47] -> [INCOMPLETE][48] ([fdo#111850])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb4/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
* igt@perf_pmu@busy-check-all-vcs1:
- shard-iclb: [PASS][49] -> [SKIP][50] ([fdo#112080]) +13 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@perf_pmu@busy-check-all-vcs1.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb5/igt@perf_pmu@busy-check-all-vcs1.html
#### Possible fixes ####
* igt@gem_busy@busy-vcs1:
- shard-iclb: [SKIP][51] ([fdo#112080]) -> [PASS][52] +16 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@gem_busy@busy-vcs1.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@gem_busy@busy-vcs1.html
* igt@gem_ctx_isolation@vecs0-s3:
- shard-kbl: [DMESG-WARN][53] ([fdo#103313]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl6/igt@gem_ctx_isolation@vecs0-s3.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl7/igt@gem_ctx_isolation@vecs0-s3.html
* igt@gem_ctx_persistence@vcs1-mixed-process:
- shard-iclb: [SKIP][55] ([fdo#109276] / [fdo#112080]) -> [PASS][56] +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@gem_ctx_persistence@vcs1-mixed-process.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@gem_ctx_persistence@vcs1-mixed-process.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][57] ([fdo#110854]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_exec_balancer@smoke.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [SKIP][59] ([fdo#112146]) -> [PASS][60] +10 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb5/igt@gem_exec_schedule@preempt-other-chain-bsd.html
* igt@gem_exec_schedule@preempt-queue-bsd2:
- shard-tglb: [INCOMPLETE][61] ([fdo#111606] / [fdo#111677]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb6/igt@gem_exec_schedule@preempt-queue-bsd2.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb2/igt@gem_exec_schedule@preempt-queue-bsd2.html
* igt@gem_persistent_relocs@forked-interruptible-thrash-inactive:
- shard-snb: [TIMEOUT][63] ([fdo#112068 ]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-snb2/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-snb6/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
* igt@gem_sync@basic-store-all:
- shard-tglb: [INCOMPLETE][65] ([fdo#111880]) -> [PASS][66] +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb6/igt@gem_sync@basic-store-all.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb7/igt@gem_sync@basic-store-all.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-hsw: [DMESG-WARN][67] ([fdo#111870]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-hsw5/igt@gem_userptr_blits@sync-unmap-cycles.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-hsw2/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@i915_pm_backlight@fade_with_suspend:
- shard-tglb: [INCOMPLETE][69] ([fdo#111832] / [fdo#111850]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb7/igt@i915_pm_backlight@fade_with_suspend.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@i915_pm_backlight@fade_with_suspend.html
* igt@kms_color@pipe-a-ctm-0-25:
- shard-skl: [DMESG-WARN][71] ([fdo#106107]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl3/igt@kms_color@pipe-a-ctm-0-25.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl2/igt@kms_color@pipe-a-ctm-0-25.html
* igt@kms_cursor_crc@pipe-a-cursor-64x64-random:
- shard-tglb: [INCOMPLETE][73] -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb6/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][75] ([fdo#108566]) -> [PASS][76] +4 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic:
- shard-skl: [FAIL][77] ([fdo#102670]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html
* igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled:
- shard-skl: [FAIL][79] ([fdo#103184] / [fdo#103232] / [fdo#108472]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@kms_draw_crc@draw-method-xrgb8888-mmap-gtt-untiled.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-tglb: [INCOMPLETE][81] ([fdo#111747] / [fdo#111832] / [fdo#111850]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@kms_fbcon_fbt@fbc-suspend.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb1/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@nonblocking-read:
- shard-kbl: [DMESG-WARN][83] ([fdo#103558] / [fdo#105602]) -> [PASS][84] +8 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-kbl3/igt@kms_flip@nonblocking-read.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-kbl6/igt@kms_flip@nonblocking-read.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-iclb: [FAIL][85] ([fdo#103167]) -> [PASS][86] +4 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt:
- shard-tglb: [FAIL][87] ([fdo#103167]) -> [PASS][88] +3 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: [DMESG-WARN][89] ([fdo#108566]) -> [PASS][90] +3 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-apl2/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][91] ([fdo#108145] / [fdo#110403]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][93] ([fdo#109441]) -> [PASS][94] +3 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb8/igt@kms_psr@psr2_sprite_plane_move.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-tglb: [INCOMPLETE][95] ([fdo#111850]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-tglb2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-tglb4/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [SKIP][97] ([fdo#109276]) -> [PASS][98] +20 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb3/igt@prime_vgem@fence-wait-bsd2.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb2/igt@prime_vgem@fence-wait-bsd2.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [SKIP][99] ([fdo#109276] / [fdo#112080]) -> [FAIL][100] ([fdo#111329]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-iclb6/igt@gem_ctx_isolation@vcs1-nonpriv.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-iclb1/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@i915_pm_dc@dc6-psr:
- shard-skl: [FAIL][101] ([fdo#111830 ]) -> [INCOMPLETE][102] ([fdo#108972])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7390/shard-skl2/igt@i915_pm_dc@dc6-psr.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/shard-skl9/igt@i915_pm_dc@dc6-psr.html
[fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103184]: https://bugs.freedesktop.org/show_bug.cgi?id=103184
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103313]: https://bugs.freedesktop.org/show_bug.cgi?id=103313
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: h
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15347/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2019-11-21 17:29 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-20 15:21 [PATCH 1/2] drm/i915: Serialise with remote retirement Chris Wilson
2019-11-20 15:21 ` [Intel-gfx] " Chris Wilson
2019-11-20 15:21 ` [PATCH 2/2] drm/i915: Remove the timeline as the last step of retiring Chris Wilson
2019-11-20 15:21 ` [Intel-gfx] " Chris Wilson
2019-11-20 16:07 ` Tvrtko Ursulin
2019-11-20 16:07 ` [Intel-gfx] " Tvrtko Ursulin
2019-11-20 16:12 ` Chris Wilson
2019-11-20 16:12 ` [Intel-gfx] " Chris Wilson
2019-11-20 16:16 ` Tvrtko Ursulin
2019-11-20 16:16 ` [Intel-gfx] " Tvrtko Ursulin
2019-11-20 16:05 ` [PATCH 1/2] drm/i915: Serialise with remote retirement Tvrtko Ursulin
2019-11-20 16:05 ` [Intel-gfx] " Tvrtko Ursulin
2019-11-20 16:08 ` Chris Wilson
2019-11-20 16:08 ` [Intel-gfx] " Chris Wilson
2019-11-20 20:50 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2019-11-20 20:50 ` [Intel-gfx] " Patchwork
2019-11-21 17:29 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-21 17:29 ` [Intel-gfx] " 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.