All of lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
@ 2018-12-11 16:16 Maarten Lankhorst
  2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Maarten Lankhorst @ 2018-12-11 16:16 UTC (permalink / raw)
  To: igt-dev; +Cc: Dhinakaran Pandiyan

Typically PSR enables in around 136 ms, but when enabling 2
screens, 500 ms is not enough on icelake sometimes, so bump
it a bit higher.

On kms_frontbuffer_tracking:
Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 350ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 1598ms

Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108733
---
 lib/igt_psr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/igt_psr.c b/lib/igt_psr.c
index 0ddfb64f0e72..265521217a2d 100644
--- a/lib/igt_psr.c
+++ b/lib/igt_psr.c
@@ -39,7 +39,7 @@ static bool psr_active(int debugfs_fd, bool check_active)
 
 bool psr_wait_entry(int debugfs_fd)
 {
-	return igt_wait(psr_active(debugfs_fd, true), 500, 20);
+	return igt_wait(psr_active(debugfs_fd, true), 2500, 20);
 }
 
 bool psr_wait_exit(int debugfs_fd)
-- 
2.19.2

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [igt-dev] ✓ Fi.CI.BAT: success for PSR: Bump wait for active timeout to 2.5s
  2018-12-11 16:16 [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s Maarten Lankhorst
@ 2018-12-11 16:48 ` Patchwork
  2018-12-11 17:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  2018-12-11 21:27 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
  2 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2018-12-11 16:48 UTC (permalink / raw)
  To: Maarten Lankhorst; +Cc: igt-dev

== Series Details ==

Series: PSR: Bump wait for active timeout to 2.5s
URL   : https://patchwork.freedesktop.org/series/53896/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_5296 -> IGTPW_2143
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/53896/revisions/1/mbox/

Known issues
------------

  Here are the changes found in IGTPW_2143 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@i915_module_load@reload:
    - {fi-kbl-7567u}:     PASS -> DMESG-WARN [fdo#103558] / [fdo#105602]

  * igt@i915_module_load@reload-with-fault-injection:
    - {fi-kbl-7567u}:     PASS -> DMESG-WARN [fdo#105602]

  * igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
    - fi-byt-clapper:     PASS -> FAIL [fdo#103191] / [fdo#107362]

  * {igt@runner@aborted}:
    - {fi-kbl-7567u}:     NOTRUN -> FAIL [fdo#105602]

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
  [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
  [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
  [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362


Participating hosts (48 -> 42)
------------------------------

  Additional (1): fi-byt-j1900 
  Missing    (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-ctg-p8600 fi-pnv-d510 fi-icl-y 


Build changes
-------------

    * IGT: IGT_4745 -> IGTPW_2143

  CI_DRM_5296: 70751bd8a3f27b035d203ecafcad452f4d7c2c15 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_2143: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2143/
  IGT_4745: 3b52e8a5809a4e860350c59476a456745cd9fee0 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2143/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [igt-dev] ✓ Fi.CI.IGT: success for PSR: Bump wait for active timeout to 2.5s
  2018-12-11 16:16 [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s Maarten Lankhorst
  2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
@ 2018-12-11 17:40 ` Patchwork
  2018-12-11 21:27 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
  2 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2018-12-11 17:40 UTC (permalink / raw)
  To: Maarten Lankhorst; +Cc: igt-dev

== Series Details ==

Series: PSR: Bump wait for active timeout to 2.5s
URL   : https://patchwork.freedesktop.org/series/53896/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_5296_full -> IGTPW_2143_full
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/53896/revisions/1/mbox/

Known issues
------------

  Here are the changes found in IGTPW_2143_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c:
    - shard-glk:          NOTRUN -> DMESG-WARN [fdo#107956]

  * igt@kms_cursor_crc@cursor-128x128-suspend:
    - shard-apl:          PASS -> FAIL [fdo#103191] / [fdo#103232] +1

  * igt@kms_cursor_crc@cursor-256x256-onscreen:
    - shard-kbl:          PASS -> FAIL [fdo#103232]

  * igt@kms_cursor_crc@cursor-256x256-random:
    - shard-glk:          PASS -> FAIL [fdo#103232] +3

  * igt@kms_cursor_crc@cursor-256x85-random:
    - shard-apl:          PASS -> FAIL [fdo#103232] +2

  * igt@kms_flip@2x-flip-vs-expired-vblank-interruptible:
    - shard-glk:          PASS -> FAIL [fdo#105363]

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu:
    - shard-kbl:          PASS -> FAIL [fdo#103167] +3

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-pwrite:
    - shard-apl:          PASS -> FAIL [fdo#103167] +4

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move:
    - shard-glk:          PASS -> FAIL [fdo#103167] +5

  * {igt@kms_plane@pixel-format-pipe-c-planes-source-clamping}:
    - shard-apl:          PASS -> FAIL [fdo#108948]

  * igt@kms_plane@plane-position-covered-pipe-b-planes:
    - shard-kbl:          PASS -> FAIL [fdo#103166]

  * igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
    - shard-glk:          PASS -> FAIL [fdo#108145]

  * igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb:
    - shard-apl:          PASS -> FAIL [fdo#108145]

  * igt@kms_plane_multiple@atomic-pipe-a-tiling-y:
    - shard-glk:          PASS -> FAIL [fdo#103166] +5

  * igt@kms_plane_multiple@atomic-pipe-b-tiling-y:
    - shard-apl:          PASS -> FAIL [fdo#103166] +3

  * igt@kms_plane_multiple@atomic-pipe-c-tiling-y:
    - shard-glk:          NOTRUN -> FAIL [fdo#103166]

  * igt@perf@polling:
    - shard-hsw:          PASS -> FAIL [fdo#102252]

  * igt@perf_pmu@rc6-runtime-pm:
    - shard-glk:          PASS -> FAIL [fdo#105010]

  
#### Possible fixes ####

  * igt@kms_cursor_crc@cursor-256x85-onscreen:
    - shard-glk:          FAIL [fdo#103232] -> PASS

  * igt@kms_cursor_crc@cursor-64x64-sliding:
    - shard-apl:          FAIL [fdo#103232] -> PASS +1
    - shard-kbl:          FAIL [fdo#103232] -> PASS

  * igt@kms_draw_crc@draw-method-rgb565-pwrite-ytiled:
    - shard-glk:          FAIL [fdo#103184] -> PASS

  * igt@kms_fbcon_fbt@fbc-suspend:
    - shard-kbl:          FAIL [fdo#103833] / [fdo#105681] -> PASS

  * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt:
    - shard-apl:          FAIL [fdo#103167] -> PASS
    - shard-kbl:          FAIL [fdo#103167] -> PASS

  * igt@kms_frontbuffer_tracking@fbc-1p-rte:
    - shard-kbl:          FAIL [fdo#103167] / [fdo#105682] -> PASS
    - shard-apl:          FAIL [fdo#103167] / [fdo#105682] -> PASS

  * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-onoff:
    - shard-glk:          FAIL [fdo#103167] -> PASS +4

  * igt@kms_plane@pixel-format-pipe-c-planes:
    - shard-apl:          FAIL [fdo#103166] -> PASS +2

  * igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
    - shard-glk:          FAIL [fdo#108145] -> PASS

  * {igt@kms_rotation_crc@multiplane-rotation-cropping-top}:
    - shard-kbl:          DMESG-FAIL [fdo#108950] -> PASS

  * igt@kms_rotation_crc@primary-rotation-180:
    - shard-snb:          FAIL [fdo#103925] -> PASS

  * igt@kms_rotation_crc@sprite-rotation-90:
    - shard-glk:          INCOMPLETE [fdo#103359] / [k.org#198133] -> PASS

  * igt@kms_universal_plane@universal-plane-pipe-b-functional:
    - shard-glk:          FAIL [fdo#103166] -> PASS +1
    - shard-kbl:          FAIL [fdo#103166] -> PASS +1

  * igt@prime_vgem@fence-wait-blt:
    - shard-snb:          DMESG-WARN [fdo#107469] -> PASS

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#102252]: https://bugs.freedesktop.org/show_bug.cgi?id=102252
  [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#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
  [fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
  [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
  [fdo#103833]: https://bugs.freedesktop.org/show_bug.cgi?id=103833
  [fdo#103925]: https://bugs.freedesktop.org/show_bug.cgi?id=103925
  [fdo#105010]: https://bugs.freedesktop.org/show_bug.cgi?id=105010
  [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
  [fdo#105681]: https://bugs.freedesktop.org/show_bug.cgi?id=105681
  [fdo#105682]: https://bugs.freedesktop.org/show_bug.cgi?id=105682
  [fdo#107469]: https://bugs.freedesktop.org/show_bug.cgi?id=107469
  [fdo#107956]: https://bugs.freedesktop.org/show_bug.cgi?id=107956
  [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
  [fdo#108948]: https://bugs.freedesktop.org/show_bug.cgi?id=108948
  [fdo#108950]: https://bugs.freedesktop.org/show_bug.cgi?id=108950
  [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133


Participating hosts (7 -> 5)
------------------------------

  Missing    (2): shard-skl shard-iclb 


Build changes
-------------

    * IGT: IGT_4745 -> IGTPW_2143
    * Piglit: piglit_4509 -> None

  CI_DRM_5296: 70751bd8a3f27b035d203ecafcad452f4d7c2c15 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_2143: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2143/
  IGT_4745: 3b52e8a5809a4e860350c59476a456745cd9fee0 @ 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_2143/
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
  2018-12-11 16:16 [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s Maarten Lankhorst
  2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
  2018-12-11 17:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
@ 2018-12-11 21:27 ` Dhinakaran Pandiyan
  2018-12-12 14:37   ` Maarten Lankhorst
  2 siblings, 1 reply; 6+ messages in thread
From: Dhinakaran Pandiyan @ 2018-12-11 21:27 UTC (permalink / raw)
  To: Maarten Lankhorst, igt-dev

On Tue, 2018-12-11 at 17:16 +0100, Maarten Lankhorst wrote:
> Typically PSR enables in around 136 ms, but when enabling 2
> screens, 500 ms is not enough on icelake sometimes, so bump
> it a bit higher.
> 
> On kms_frontbuffer_tracking:
> Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
> psr_active(debugfs_fd, true) took 136ms
> psr_active(debugfs_fd, true) took 136ms
> psr_active(debugfs_fd, true) took 350ms
> psr_active(debugfs_fd, true) took 136ms
> psr_active(debugfs_fd, true) took 1598ms

We have to find out why it took that long, ~96 frames exceeds the idle
frame limit we set in the driver. I'm concerned we might be covering up
a bug by increasing the limit so high.

-DK

> 
> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108733
> ---
>  lib/igt_psr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/igt_psr.c b/lib/igt_psr.c
> index 0ddfb64f0e72..265521217a2d 100644
> --- a/lib/igt_psr.c
> +++ b/lib/igt_psr.c
> @@ -39,7 +39,7 @@ static bool psr_active(int debugfs_fd, bool
> check_active)
>  
>  bool psr_wait_entry(int debugfs_fd)
>  {
> -	return igt_wait(psr_active(debugfs_fd, true), 500, 20);
> +	return igt_wait(psr_active(debugfs_fd, true), 2500, 20);
>  }
>  
>  bool psr_wait_exit(int debugfs_fd)

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
  2018-12-11 21:27 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
@ 2018-12-12 14:37   ` Maarten Lankhorst
  2018-12-12 15:11     ` Chris Wilson
  0 siblings, 1 reply; 6+ messages in thread
From: Maarten Lankhorst @ 2018-12-12 14:37 UTC (permalink / raw)
  To: dhinakaran.pandiyan, igt-dev

Op 11-12-2018 om 22:27 schreef Dhinakaran Pandiyan:
> On Tue, 2018-12-11 at 17:16 +0100, Maarten Lankhorst wrote:
>> Typically PSR enables in around 136 ms, but when enabling 2
>> screens, 500 ms is not enough on icelake sometimes, so bump
>> it a bit higher.
>>
>> On kms_frontbuffer_tracking:
>> Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
>> psr_active(debugfs_fd, true) took 136ms
>> psr_active(debugfs_fd, true) took 136ms
>> psr_active(debugfs_fd, true) took 350ms
>> psr_active(debugfs_fd, true) took 136ms
>> psr_active(debugfs_fd, true) took 1598ms
> We have to find out why it took that long, ~96 frames exceeds the idle
> frame limit we set in the driver. I'm concerned we might be covering up
> a bug by increasing the limit so high.

After some debugging, it seems retiring the gem workqueue causes the delay..

[   90.244237] Activating PSR from 2
[   90.244378] WARNING: CPU: 3 PID: 181 at drivers/gpu/drm/i915/intel_psr.c:1143 intel_psr_flush+0xe3/0x100 [i915]
...
[   90.244672] Call Trace:
[   90.244776]  intel_frontbuffer_flush+0x6a/0x80 [i915]
[   90.244893]  i915_request_retire+0x189/0x930 [i915]
[   90.245019]  i915_retire_requests+0xa5/0x130 [i915]
[   90.245134]  i915_gem_retire_work_handler+0x59/0x70 [i915]
[   90.245152]  process_one_work+0x262/0x630
[   90.245181]  worker_thread+0x37/0x380
[   90.245199]  ? process_one_work+0x630/0x630
[   90.245209]  kthread+0x119/0x130
[   90.245220]  ? kthread_park+0x80/0x80
[   90.245238]  ret_from_fork+0x3a/0x50
[   90.245278] irq event stamp: 30662
[   90.245290] hardirqs last  enabled at (30661): [<ffffffff810fb0a9>] console_unlock+0x3f9/0x5f0
[   90.245300] hardirqs last disabled at (30662): [<ffffffff810019b0>] trace_hardirqs_off_thunk+0x1a/0x1c
[   90.245310] softirqs last  enabled at (30644): [<ffffffff81c0033a>] __do_softirq+0x33a/0x4b9
[   90.245322] softirqs last disabled at (30631): [<ffffffff8108e6a9>] irq_exit+0xa9/0xc0
..
[   90.246941] [drm:intel_psr_work [i915]] Activating PSR1
[   90.335272] [drm:intel_psr_irq_handler [i915]] [transcoder EDP] PSR entry attempt in 2 vblanks

Which seems to come from i915_gem_unpark() ?

~Maarten

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
  2018-12-12 14:37   ` Maarten Lankhorst
@ 2018-12-12 15:11     ` Chris Wilson
  0 siblings, 0 replies; 6+ messages in thread
From: Chris Wilson @ 2018-12-12 15:11 UTC (permalink / raw)
  To: Maarten Lankhorst, dhinakaran.pandiyan, igt-dev

Quoting Maarten Lankhorst (2018-12-12 14:37:59)
> Op 11-12-2018 om 22:27 schreef Dhinakaran Pandiyan:
> > On Tue, 2018-12-11 at 17:16 +0100, Maarten Lankhorst wrote:
> >> Typically PSR enables in around 136 ms, but when enabling 2
> >> screens, 500 ms is not enough on icelake sometimes, so bump
> >> it a bit higher.
> >>
> >> On kms_frontbuffer_tracking:
> >> Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
> >> psr_active(debugfs_fd, true) took 136ms
> >> psr_active(debugfs_fd, true) took 136ms
> >> psr_active(debugfs_fd, true) took 350ms
> >> psr_active(debugfs_fd, true) took 136ms
> >> psr_active(debugfs_fd, true) took 1598ms
> > We have to find out why it took that long, ~96 frames exceeds the idle
> > frame limit we set in the driver. I'm concerned we might be covering up
> > a bug by increasing the limit so high.
> 
> After some debugging, it seems retiring the gem workqueue causes the delay..
> 
> [   90.244237] Activating PSR from 2
> [   90.244378] WARNING: CPU: 3 PID: 181 at drivers/gpu/drm/i915/intel_psr.c:1143 intel_psr_flush+0xe3/0x100 [i915]
> ...
> [   90.244672] Call Trace:
> [   90.244776]  intel_frontbuffer_flush+0x6a/0x80 [i915]
> [   90.244893]  i915_request_retire+0x189/0x930 [i915]
> [   90.245019]  i915_retire_requests+0xa5/0x130 [i915]
> [   90.245134]  i915_gem_retire_work_handler+0x59/0x70 [i915]
> [   90.245152]  process_one_work+0x262/0x630
> [   90.245181]  worker_thread+0x37/0x380
> [   90.245199]  ? process_one_work+0x630/0x630
> [   90.245209]  kthread+0x119/0x130
> [   90.245220]  ? kthread_park+0x80/0x80
> [   90.245238]  ret_from_fork+0x3a/0x50
> [   90.245278] irq event stamp: 30662
> [   90.245290] hardirqs last  enabled at (30661): [<ffffffff810fb0a9>] console_unlock+0x3f9/0x5f0
> [   90.245300] hardirqs last disabled at (30662): [<ffffffff810019b0>] trace_hardirqs_off_thunk+0x1a/0x1c
> [   90.245310] softirqs last  enabled at (30644): [<ffffffff81c0033a>] __do_softirq+0x33a/0x4b9
> [   90.245322] softirqs last disabled at (30631): [<ffffffff8108e6a9>] irq_exit+0xa9/0xc0
> ..
> [   90.246941] [drm:intel_psr_work [i915]] Activating PSR1
> [   90.335272] [drm:intel_psr_irq_handler [i915]] [transcoder EDP] PSR entry attempt in 2 vblanks
> 
> Which seems to come from i915_gem_unpark() ?

You rendered into the frontbuffer and then left it alone, leaving it to
the bg flusher. If you use
	igt_drop_caches_set(DROP_ACTIVE | DROP_RETIRE | DROP_IDLE)
(or just gem_quiescent_gpu()) that will flush the retirement queue.

The gem_unpark is misleading, you don't need the DROP_IDLE, as you just
need the outstanding retirements.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2018-12-12 15:11 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-11 16:16 [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s Maarten Lankhorst
2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-12-11 17:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-12-11 21:27 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
2018-12-12 14:37   ` Maarten Lankhorst
2018-12-12 15:11     ` Chris Wilson

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.