* [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
@ 2020-12-03 8:39 Chris Wilson
2020-12-03 9:26 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Chris Wilson @ 2020-12-03 8:39 UTC (permalink / raw)
To: intel-gfx; +Cc: igt-dev, Chris Wilson
If we let an object idle in a shared GTT, it may be evicted by the
kernel in favour of another client. Thus, we have to be very careful
when asserting that two different executions of the same object will
be at the same address. If there's an idle point between the two
asserts, it will only be guaranteed to hold for full-ppgtt.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
---
tests/i915/api_intel_bb.c | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
index 0cb3192cb..18814d14d 100644
--- a/tests/i915/api_intel_bb.c
+++ b/tests/i915/api_intel_bb.c
@@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
check_buf(dst, COLOR_77);
- poff2_src = intel_bb_get_object_offset(ibb, src->handle);
- poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
- igt_assert(poff_src == poff2_src);
- igt_assert(poff_dst == poff2_dst);
+ /*
+ * Since we let the objects idle, if the GTT is shared another client
+ * is liable to reuse our offsets for themselves, causing us to have
+ * to relocate. We don't expect this to happen as LRU eviction should
+ * try to avoid reuse, but we use random eviction instead as it is
+ * much quicker! Given that the kernel is *allowed* to relocate objects,
+ * we cannot assert that the objects remain in the same location, unless
+ * we are in full control of our own GTT.
+ */
+ if (gem_uses_full_ppgtt(i915)) {
+ igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
+ poff_src);
+ igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
+ poff_dst);
+ }
intel_buf_destroy(src);
intel_buf_destroy(dst);
--
2.29.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 7+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
2020-12-03 8:39 [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt Chris Wilson
@ 2020-12-03 9:26 ` Patchwork
2020-12-03 10:34 ` [igt-dev] " Zbigniew Kempczyński
2020-12-03 12:26 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2020-12-03 9:26 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 3011 bytes --]
== Series Details ==
Series: i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
URL : https://patchwork.freedesktop.org/series/84527/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9430 -> IGTPW_5246
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
Known issues
------------
Here are the changes found in IGTPW_5246 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_sync@basic-each:
- fi-kbl-guc: [PASS][1] -> [INCOMPLETE][2] ([i915#794])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/fi-kbl-guc/igt@gem_sync@basic-each.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/fi-kbl-guc/igt@gem_sync@basic-each.html
* igt@prime_self_import@basic-with_two_bos:
- fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/fi-tgl-y/igt@prime_self_import@basic-with_two_bos.html
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- fi-kbl-7500u: [DMESG-WARN][5] ([i915#2605]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/fi-kbl-7500u/igt@core_hotunplug@unbind-rebind.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/fi-kbl-7500u/igt@core_hotunplug@unbind-rebind.html
* igt@prime_self_import@basic-with_one_bo_two_files:
- fi-tgl-y: [DMESG-WARN][7] ([i915#402]) -> [PASS][8] +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#2605]: https://gitlab.freedesktop.org/drm/intel/issues/2605
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
Participating hosts (42 -> 40)
------------------------------
Additional (2): fi-blb-e6850 fi-tgl-dsi
Missing (4): fi-ilk-m540 fi-dg1-1 fi-bdw-samus fi-hsw-4200u
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5878 -> IGTPW_5246
CI-20190529: 20190529
CI_DRM_9430: 88c5c7135da4f61235fe3dbf4a67b2121b893fca @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5246: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
IGT_5878: e96c0d8e6952d892bcbbcdf004999880a4dfb42e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
[-- Attachment #1.2: Type: text/html, Size: 3782 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
2020-12-03 8:39 [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt Chris Wilson
@ 2020-12-03 10:34 ` Zbigniew Kempczyński
2020-12-03 10:34 ` [igt-dev] " Zbigniew Kempczyński
2020-12-03 12:26 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2 siblings, 0 replies; 7+ messages in thread
From: Zbigniew Kempczyński @ 2020-12-03 10:34 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev, intel-gfx
On Thu, Dec 03, 2020 at 08:39:31AM +0000, Chris Wilson wrote:
> If we let an object idle in a shared GTT, it may be evicted by the
> kernel in favour of another client. Thus, we have to be very careful
> when asserting that two different executions of the same object will
> be at the same address. If there's an idle point between the two
> asserts, it will only be guaranteed to hold for full-ppgtt.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> ---
> tests/i915/api_intel_bb.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
> index 0cb3192cb..18814d14d 100644
> --- a/tests/i915/api_intel_bb.c
> +++ b/tests/i915/api_intel_bb.c
> @@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
> intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
> check_buf(dst, COLOR_77);
>
> - poff2_src = intel_bb_get_object_offset(ibb, src->handle);
> - poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
> - igt_assert(poff_src == poff2_src);
> - igt_assert(poff_dst == poff2_dst);
> + /*
> + * Since we let the objects idle, if the GTT is shared another client
> + * is liable to reuse our offsets for themselves, causing us to have
> + * to relocate. We don't expect this to happen as LRU eviction should
> + * try to avoid reuse, but we use random eviction instead as it is
> + * much quicker! Given that the kernel is *allowed* to relocate objects,
> + * we cannot assert that the objects remain in the same location, unless
> + * we are in full control of our own GTT.
> + */
> + if (gem_uses_full_ppgtt(i915)) {
> + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
> + poff_src);
> + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
> + poff_dst);
> + }
>
> intel_buf_destroy(src);
> intel_buf_destroy(dst);
> --
> 2.29.2
>
Patch looks ok. BTW is it possible when we're running the test in isolated
environment (IGT)?
Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
--
Zbigniew
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
@ 2020-12-03 10:34 ` Zbigniew Kempczyński
0 siblings, 0 replies; 7+ messages in thread
From: Zbigniew Kempczyński @ 2020-12-03 10:34 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev, intel-gfx
On Thu, Dec 03, 2020 at 08:39:31AM +0000, Chris Wilson wrote:
> If we let an object idle in a shared GTT, it may be evicted by the
> kernel in favour of another client. Thus, we have to be very careful
> when asserting that two different executions of the same object will
> be at the same address. If there's an idle point between the two
> asserts, it will only be guaranteed to hold for full-ppgtt.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> ---
> tests/i915/api_intel_bb.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
> index 0cb3192cb..18814d14d 100644
> --- a/tests/i915/api_intel_bb.c
> +++ b/tests/i915/api_intel_bb.c
> @@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
> intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
> check_buf(dst, COLOR_77);
>
> - poff2_src = intel_bb_get_object_offset(ibb, src->handle);
> - poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
> - igt_assert(poff_src == poff2_src);
> - igt_assert(poff_dst == poff2_dst);
> + /*
> + * Since we let the objects idle, if the GTT is shared another client
> + * is liable to reuse our offsets for themselves, causing us to have
> + * to relocate. We don't expect this to happen as LRU eviction should
> + * try to avoid reuse, but we use random eviction instead as it is
> + * much quicker! Given that the kernel is *allowed* to relocate objects,
> + * we cannot assert that the objects remain in the same location, unless
> + * we are in full control of our own GTT.
> + */
> + if (gem_uses_full_ppgtt(i915)) {
> + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
> + poff_src);
> + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
> + poff_dst);
> + }
>
> intel_buf_destroy(src);
> intel_buf_destroy(dst);
> --
> 2.29.2
>
Patch looks ok. BTW is it possible when we're running the test in isolated
environment (IGT)?
Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
--
Zbigniew
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
2020-12-03 10:34 ` [igt-dev] " Zbigniew Kempczyński
@ 2020-12-03 10:51 ` Chris Wilson
-1 siblings, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2020-12-03 10:51 UTC (permalink / raw)
To: Zbigniew Kempczyński; +Cc: igt-dev, intel-gfx
Quoting Zbigniew Kempczyński (2020-12-03 10:34:23)
> On Thu, Dec 03, 2020 at 08:39:31AM +0000, Chris Wilson wrote:
> > If we let an object idle in a shared GTT, it may be evicted by the
> > kernel in favour of another client. Thus, we have to be very careful
> > when asserting that two different executions of the same object will
> > be at the same address. If there's an idle point between the two
> > asserts, it will only be guaranteed to hold for full-ppgtt.
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> > ---
> > tests/i915/api_intel_bb.c | 19 +++++++++++++++----
> > 1 file changed, 15 insertions(+), 4 deletions(-)
> >
> > diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
> > index 0cb3192cb..18814d14d 100644
> > --- a/tests/i915/api_intel_bb.c
> > +++ b/tests/i915/api_intel_bb.c
> > @@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
> > intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
> > check_buf(dst, COLOR_77);
> >
> > - poff2_src = intel_bb_get_object_offset(ibb, src->handle);
> > - poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
> > - igt_assert(poff_src == poff2_src);
> > - igt_assert(poff_dst == poff2_dst);
> > + /*
> > + * Since we let the objects idle, if the GTT is shared another client
> > + * is liable to reuse our offsets for themselves, causing us to have
> > + * to relocate. We don't expect this to happen as LRU eviction should
> > + * try to avoid reuse, but we use random eviction instead as it is
> > + * much quicker! Given that the kernel is *allowed* to relocate objects,
> > + * we cannot assert that the objects remain in the same location, unless
> > + * we are in full control of our own GTT.
> > + */
> > + if (gem_uses_full_ppgtt(i915)) {
> > + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
> > + poff_src);
> > + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
> > + poff_dst);
> > + }
> >
> > intel_buf_destroy(src);
> > intel_buf_destroy(dst);
> > --
> > 2.29.2
> >
>
> Patch looks ok. BTW is it possible when we're running the test in isolated
> environment (IGT)?
Never say never. The kernel does do things in the background (e.g.
responding to hotplug with fbcon) that may cause the global GTT to be
evicted, and we do some background work for heartbeats and the like (but
they should all be statically placed, so unlikely).
GTT mmapping is another possible cause, since the preference is to keep
the whole object as a single mmapped vma, and so we may move an existing
vma used for the execbuf to a mappable location. (Only if idle at the
time, otherwise we create a new vma for the mmap.)
The devil is in the details, and it's much easier to say that if not
using full-ppgtt, expect relocations.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
@ 2020-12-03 10:51 ` Chris Wilson
0 siblings, 0 replies; 7+ messages in thread
From: Chris Wilson @ 2020-12-03 10:51 UTC (permalink / raw)
To: zbigniew.kempczynski; +Cc: igt-dev, intel-gfx
Quoting Zbigniew Kempczyński (2020-12-03 10:34:23)
> On Thu, Dec 03, 2020 at 08:39:31AM +0000, Chris Wilson wrote:
> > If we let an object idle in a shared GTT, it may be evicted by the
> > kernel in favour of another client. Thus, we have to be very careful
> > when asserting that two different executions of the same object will
> > be at the same address. If there's an idle point between the two
> > asserts, it will only be guaranteed to hold for full-ppgtt.
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2754
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> > ---
> > tests/i915/api_intel_bb.c | 19 +++++++++++++++----
> > 1 file changed, 15 insertions(+), 4 deletions(-)
> >
> > diff --git a/tests/i915/api_intel_bb.c b/tests/i915/api_intel_bb.c
> > index 0cb3192cb..18814d14d 100644
> > --- a/tests/i915/api_intel_bb.c
> > +++ b/tests/i915/api_intel_bb.c
> > @@ -505,10 +505,21 @@ static void blit(struct buf_ops *bops,
> > intel_bb_exec(ibb, intel_bb_offset(ibb), flags, true);
> > check_buf(dst, COLOR_77);
> >
> > - poff2_src = intel_bb_get_object_offset(ibb, src->handle);
> > - poff2_dst = intel_bb_get_object_offset(ibb, dst->handle);
> > - igt_assert(poff_src == poff2_src);
> > - igt_assert(poff_dst == poff2_dst);
> > + /*
> > + * Since we let the objects idle, if the GTT is shared another client
> > + * is liable to reuse our offsets for themselves, causing us to have
> > + * to relocate. We don't expect this to happen as LRU eviction should
> > + * try to avoid reuse, but we use random eviction instead as it is
> > + * much quicker! Given that the kernel is *allowed* to relocate objects,
> > + * we cannot assert that the objects remain in the same location, unless
> > + * we are in full control of our own GTT.
> > + */
> > + if (gem_uses_full_ppgtt(i915)) {
> > + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, src->handle),
> > + poff_src);
> > + igt_assert_eq_u64(intel_bb_get_object_offset(ibb, dst->handle),
> > + poff_dst);
> > + }
> >
> > intel_buf_destroy(src);
> > intel_buf_destroy(dst);
> > --
> > 2.29.2
> >
>
> Patch looks ok. BTW is it possible when we're running the test in isolated
> environment (IGT)?
Never say never. The kernel does do things in the background (e.g.
responding to hotplug with fbcon) that may cause the global GTT to be
evicted, and we do some background work for heartbeats and the like (but
they should all be statically placed, so unlikely).
GTT mmapping is another possible cause, since the preference is to keep
the whole object as a single mmapped vma, and so we may move an existing
vma used for the execbuf to a mappable location. (Only if idle at the
time, otherwise we create a new vma for the mmap.)
The devil is in the details, and it's much easier to say that if not
using full-ppgtt, expect relocations.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
2020-12-03 8:39 [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt Chris Wilson
2020-12-03 9:26 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-12-03 10:34 ` [igt-dev] " Zbigniew Kempczyński
@ 2020-12-03 12:26 ` Patchwork
2 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2020-12-03 12:26 UTC (permalink / raw)
To: Chris Wilson; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 19015 bytes --]
== Series Details ==
Series: i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt
URL : https://patchwork.freedesktop.org/series/84527/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9430_full -> IGTPW_5246_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5246_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5246_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5246_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_legacy@pipe-b-single-bo:
- shard-hsw: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-hsw1/igt@kms_cursor_legacy@pipe-b-single-bo.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-hsw7/igt@kms_cursor_legacy@pipe-b-single-bo.html
#### Warnings ####
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-pwrite:
- shard-kbl: [SKIP][3] ([fdo#109271]) -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-pwrite.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-pwrite.html
Known issues
------------
Here are the changes found in IGTPW_5246_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@reg-read-ioctl:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#579])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb2/igt@i915_pm_rpm@reg-read-ioctl.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb6/igt@i915_pm_rpm@reg-read-ioctl.html
- shard-hsw: [PASS][7] -> [SKIP][8] ([fdo#109271])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-hsw1/igt@i915_pm_rpm@reg-read-ioctl.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-hsw2/igt@i915_pm_rpm@reg-read-ioctl.html
- shard-tglb: [PASS][9] -> [SKIP][10] ([i915#579])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb5/igt@i915_pm_rpm@reg-read-ioctl.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb1/igt@i915_pm_rpm@reg-read-ioctl.html
- shard-kbl: [PASS][11] -> [SKIP][12] ([fdo#109271])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl6/igt@i915_pm_rpm@reg-read-ioctl.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl7/igt@i915_pm_rpm@reg-read-ioctl.html
- shard-apl: [PASS][13] -> [SKIP][14] ([fdo#109271])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl6/igt@i915_pm_rpm@reg-read-ioctl.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl6/igt@i915_pm_rpm@reg-read-ioctl.html
- shard-glk: [PASS][15] -> [SKIP][16] ([fdo#109271])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk2/igt@i915_pm_rpm@reg-read-ioctl.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk2/igt@i915_pm_rpm@reg-read-ioctl.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][17] -> [INCOMPLETE][18] ([i915#155] / [i915#180] / [i915#2295])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1:
- shard-tglb: [PASS][19] -> [FAIL][20] ([i915#2122])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb5/igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb7/igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1.html
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-tglb: [PASS][21] -> [FAIL][22] ([i915#2598])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb7/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb2/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [PASS][23] -> [INCOMPLETE][24] ([i915#155] / [i915#180])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl1/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl4/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-iclb: [PASS][25] -> [INCOMPLETE][26] ([i915#1185] / [i915#250])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
- shard-apl: [PASS][27] -> [INCOMPLETE][28] ([i915#2635])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
- shard-glk: [PASS][29] -> [INCOMPLETE][30] ([i915#2635])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk2/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
- shard-hsw: [PASS][31] -> [INCOMPLETE][32] ([i915#2055] / [i915#2637])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-hsw1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-hsw2/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
- shard-tglb: [PASS][33] -> [INCOMPLETE][34] ([i915#1436] / [i915#1798] / [i915#1982] / [i915#456])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb1/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
- shard-kbl: [PASS][35] -> [INCOMPLETE][36] ([i915#155])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl7/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb7/igt@kms_psr@psr2_sprite_plane_move.html
#### Possible fixes ####
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-apl: [FAIL][39] ([i915#2389]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl7/igt@gem_exec_reloc@basic-many-active@rcs0.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl7/igt@gem_exec_reloc@basic-many-active@rcs0.html
- shard-glk: [FAIL][41] ([i915#2389]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk9/igt@gem_exec_reloc@basic-many-active@rcs0.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk6/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_fenced_exec_thrash@no-spare-fences:
- shard-hsw: [INCOMPLETE][43] ([i915#2055]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-hsw1/igt@gem_fenced_exec_thrash@no-spare-fences.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-hsw1/igt@gem_fenced_exec_thrash@no-spare-fences.html
* igt@i915_pm_rpm@system-suspend-execbuf:
- shard-iclb: [SKIP][45] ([i915#579]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb8/igt@i915_pm_rpm@system-suspend-execbuf.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb8/igt@i915_pm_rpm@system-suspend-execbuf.html
- shard-kbl: [SKIP][47] ([fdo#109271]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl1/igt@i915_pm_rpm@system-suspend-execbuf.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl4/igt@i915_pm_rpm@system-suspend-execbuf.html
- shard-apl: [SKIP][49] ([fdo#109271]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl1/igt@i915_pm_rpm@system-suspend-execbuf.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl2/igt@i915_pm_rpm@system-suspend-execbuf.html
- shard-tglb: [SKIP][51] ([i915#579]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb5/igt@i915_pm_rpm@system-suspend-execbuf.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb7/igt@i915_pm_rpm@system-suspend-execbuf.html
- shard-glk: [SKIP][53] ([fdo#109271]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk1/igt@i915_pm_rpm@system-suspend-execbuf.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk3/igt@i915_pm_rpm@system-suspend-execbuf.html
* igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@edp-1-pipe-d:
- shard-tglb: [INCOMPLETE][55] -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb6/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@edp-1-pipe-d.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb2/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@edp-1-pipe-d.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-tglb: [FAIL][57] ([i915#2598]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb7/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb1/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
* igt@kms_plane_lowres@pipe-c-tiling-y:
- shard-kbl: [DMESG-WARN][59] ([i915#165] / [i915#180] / [i915#78]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl2/igt@kms_plane_lowres@pipe-c-tiling-y.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl3/igt@kms_plane_lowres@pipe-c-tiling-y.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [SKIP][61] ([fdo#109441]) -> [PASS][62] +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb7/igt@kms_psr@psr2_cursor_render.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm:
- shard-hsw: [SKIP][63] ([fdo#109271]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-hsw2/igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-hsw2/igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm.html
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][65] ([i915#1804] / [i915#2684]) -> [WARN][66] ([i915#2681] / [i915#2684])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb3/igt@i915_pm_rc6_residency@rc6-idle.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@runner@aborted:
- shard-kbl: [FAIL][67] ([i915#2295] / [i915#2722]) -> ([FAIL][68], [FAIL][69], [FAIL][70], [FAIL][71], [FAIL][72]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [i915#92])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-kbl7/igt@runner@aborted.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl7/igt@runner@aborted.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl4/igt@runner@aborted.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl7/igt@runner@aborted.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl4/igt@runner@aborted.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-kbl2/igt@runner@aborted.html
- shard-iclb: ([FAIL][73], [FAIL][74]) ([i915#2295] / [i915#2722] / [i915#483]) -> ([FAIL][75], [FAIL][76], [FAIL][77]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb8/igt@runner@aborted.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-iclb5/igt@runner@aborted.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb6/igt@runner@aborted.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb3/igt@runner@aborted.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-iclb2/igt@runner@aborted.html
- shard-apl: ([FAIL][78], [FAIL][79]) ([i915#2295] / [i915#2722]) -> ([FAIL][80], [FAIL][81], [FAIL][82]) ([i915#1814] / [i915#2295] / [i915#2722])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl1/igt@runner@aborted.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-apl1/igt@runner@aborted.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl8/igt@runner@aborted.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl6/igt@runner@aborted.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-apl4/igt@runner@aborted.html
- shard-glk: ([FAIL][83], [FAIL][84]) ([i915#2295] / [i915#2722] / [k.org#202321]) -> ([FAIL][85], [FAIL][86], [FAIL][87]) ([i915#1814] / [i915#2295] / [i915#2722] / [i915#483] / [k.org#202321])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk1/igt@runner@aborted.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-glk1/igt@runner@aborted.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk2/igt@runner@aborted.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk7/igt@runner@aborted.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-glk2/igt@runner@aborted.html
- shard-tglb: ([FAIL][88], [FAIL][89]) ([i915#1602] / [i915#2295] / [i915#2722]) -> ([FAIL][90], [FAIL][91], [FAIL][92]) ([i915#1602] / [i915#1814] / [i915#2295] / [i915#2722])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb8/igt@runner@aborted.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9430/shard-tglb5/igt@runner@aborted.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb2/igt@runner@aborted.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb1/igt@runner@aborted.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/shard-tglb1/igt@runner@aborted.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[i915#1185]: https://gitlab.freedesktop.org/drm/intel/issues/1185
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#1798]: https://gitlab.freedesktop.org/drm/intel/issues/1798
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2055]: https://gitlab.freedesktop.org/drm/intel/issues/2055
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2295]: https://gitlab.freedesktop.org/drm/intel/issues/2295
[i915#2389]: https://gitlab.freedesktop.org/drm/intel/issues/2389
[i915#250]: https://gitlab.freedesktop.org/drm/intel/issues/250
[i915#2574]: https://gitlab.freedesktop.org/drm/intel/issues/2574
[i915#2598]: https://gitlab.freedesktop.org/drm/intel/issues/2598
[i915#2635]: https://gitlab.freedesktop.org/drm/intel/issues/2635
[i915#2637]: https://gitlab.freedesktop.org/drm/intel/issues/2637
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#483]: https://gitlab.freedesktop.org/drm/intel/issues/483
[i915#579]: https://gitlab.freedesktop.org/drm/intel/issues/579
[i915#78]: https://gitlab.freedesktop.org/drm/intel/issues/78
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Participating hosts (10 -> 8)
------------------------------
Missing (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5878 -> IGTPW_5246
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_9430: 88c5c7135da4f61235fe3dbf4a67b2121b893fca @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5246: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
IGT_5878: e96c0d8e6952d892bcbbcdf004999880a4dfb42e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5246/index.html
[-- Attachment #1.2: Type: text/html, Size: 23711 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2020-12-03 12:26 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-03 8:39 [Intel-gfx] [PATCH i-g-t] i915/api_intel_bb: Only assert objects are unmoved for full-ppgtt Chris Wilson
2020-12-03 9:26 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-12-03 10:34 ` [Intel-gfx] [PATCH i-g-t] " Zbigniew Kempczyński
2020-12-03 10:34 ` [igt-dev] " Zbigniew Kempczyński
2020-12-03 10:51 ` [Intel-gfx] " Chris Wilson
2020-12-03 10:51 ` Chris Wilson
2020-12-03 12:26 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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.