Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: ✓ Fi.CI.BAT: success for Restore workarounds after engine reset and unify their handling (rev8)
Date: Tue, 4 Dec 2018 13:02:09 +0000	[thread overview]
Message-ID: <578024b7-316d-f487-2aa2-7a1e7fad4a44@linux.intel.com> (raw)
In-Reply-To: <20181204084140.4002.27011@emeril.freedesktop.org>


On 04/12/2018 08:41, Patchwork wrote:
> == Series Details ==
> 
> Series: Restore workarounds after engine reset and unify their handling (rev8)
> URL   : https://patchwork.freedesktop.org/series/53313/
> State : success
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_5247 -> Patchwork_11000
> ====================================================
> 
> Summary
> -------
> 
>    **SUCCESS**
> 
>    No regressions found.
> 
>    External URL: https://patchwork.freedesktop.org/api/1.0/series/53313/revisions/8/mbox/
> 
> Known issues
> ------------
> 
>    Here are the changes found in Patchwork_11000 that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>    * igt@i915_selftest@live_hangcheck:
>      - fi-bwr-2160:        PASS -> DMESG-FAIL [fdo#108735]
> 
>    * igt@prime_vgem@basic-fence-flip:
>      - fi-ilk-650:         PASS -> FAIL [fdo#104008]
> 
>    
> #### Possible fixes ####
> 
>    * igt@gem_ctx_create@basic-files:
>      - fi-bsw-n3050:       FAIL [fdo#108656] -> PASS
> 
>    * igt@gem_exec_suspend@basic-s3:
>      - fi-cfl-8109u:       DMESG-WARN [fdo#107345] -> PASS +3
> 
>    * igt@i915_selftest@live_evict:
>      - fi-bsw-kefka:       DMESG-WARN [fdo#107709] -> PASS
> 
>    
>    [fdo#104008]: https://bugs.freedesktop.org/show_bug.cgi?id=104008
>    [fdo#107345]: https://bugs.freedesktop.org/show_bug.cgi?id=107345
>    [fdo#107709]: https://bugs.freedesktop.org/show_bug.cgi?id=107709
>    [fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656
>    [fdo#108735]: https://bugs.freedesktop.org/show_bug.cgi?id=108735
> 
> 
> Participating hosts (48 -> 43)
> ------------------------------
> 
>    Missing    (5): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600
> 
> 
> Build changes
> -------------
> 
>      * Linux: CI_DRM_5247 -> Patchwork_11000
> 
>    CI_DRM_5247: ff3d336ae5b3ef75e12ed400fd4ccb55701c212a @ git://anongit.freedesktop.org/gfx-ci/linux
>    IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>    Patchwork_11000: d4c5c1e46f449f42f10520d0af9208a02f05dca8 @ git://anongit.freedesktop.org/gfx-ci/linux
> 
> 
> == Linux commits ==
> 
> d4c5c1e46f44 drm/i915: Trim unused workaround list entries
> 3a2e4194081e drm/i915: Fuse per-context workaround handling with the common framework
> 6997332fc8d8 drm/i915: Move register white-listing to the common workaround framework
> 5eb7b5ed728b drm/i915/selftests: Add tests for GT and engine workaround verification
> b48dab8be432 drm/i915: Verify GT workaround state after GPU init
> 68a4800dce59 drm/i915: Introduce per-engine workarounds
> e2c45229710e drm/i915: Record GT workarounds in a list

Pushed, thanks for the reviews and lets hope there are some collateral 
fixes from this.

Regards,

Tvrtko


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-12-04 13:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 12:50 [PATCH v4 0/7] Restore workarounds after engine reset and unify their handling Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 1/7] drm/i915: Record GT workarounds in a list Tvrtko Ursulin
2018-12-03 12:53   ` Chris Wilson
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 2/7] drm/i915: Introduce per-engine workarounds Tvrtko Ursulin
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 3/7] drm/i915: Verify GT workaround state after GPU init Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 4/7] drm/i915/selftests: Add tests for GT and engine workaround verification Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 5/7] drm/i915: Move register white-listing to the common workaround framework Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 6/7] drm/i915: Fuse per-context workaround handling with the common framework Tvrtko Ursulin
2018-12-03 13:33   ` Tvrtko Ursulin
2018-12-03 12:50 ` [PATCH 7/7] drm/i915: Trim unused workaround list entries Tvrtko Ursulin
2018-12-03 12:52   ` Chris Wilson
2018-12-03 13:05 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev4) Patchwork
2018-12-03 13:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-03 13:36 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-03 14:40 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev7) Patchwork
2018-12-03 14:43 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-03 14:56 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-12-03 17:23 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev8) Patchwork
2018-12-03 17:26 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-04  8:01 ` ✗ Fi.CI.CHECKPATCH: warning for Restore workarounds after engine reset and unify their handling (rev9) Patchwork
2018-12-04  8:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-12-04  8:22 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-04  8:41 ` ✓ Fi.CI.BAT: success for Restore workarounds after engine reset and unify their handling (rev8) Patchwork
2018-12-04 13:02   ` Tvrtko Ursulin [this message]
2018-12-04  9:42 ` ✓ Fi.CI.IGT: success for Restore workarounds after engine reset and unify their handling (rev9) Patchwork
2018-12-04 12:12   ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=578024b7-316d-f487-2aa2-7a1e7fad4a44@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox