* [Intel-gfx] [PATCH] drm/i915: Manually acquire engine-wakeref around use of kernel_context
@ 2020-02-24 23:31 Chris Wilson
2020-02-24 23:48 ` Chris Wilson
2020-02-25 0:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
0 siblings, 2 replies; 3+ messages in thread
From: Chris Wilson @ 2020-02-24 23:31 UTC (permalink / raw)
To: intel-gfx
The engine->kernel_context is a special case for request emission. Since
it is used as the barrier within the engine's wakeref, we must acquire the
wakeref before submitting a request to the kernel_context.
Reported-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
---
drivers/gpu/drm/i915/i915_perf.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index e34c79df6ebc..c3cea33578b5 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -2194,7 +2194,9 @@ static int gen8_modify_self(struct intel_context *ce,
struct i915_request *rq;
int err;
+ intel_engine_pm_get(ce->engine);
rq = i915_request_create(ce);
+ intel_engine_pm_put(ce->engine);
if (IS_ERR(rq))
return PTR_ERR(rq);
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Manually acquire engine-wakeref around use of kernel_context
2020-02-24 23:31 [Intel-gfx] [PATCH] drm/i915: Manually acquire engine-wakeref around use of kernel_context Chris Wilson
@ 2020-02-24 23:48 ` Chris Wilson
2020-02-25 0:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
1 sibling, 0 replies; 3+ messages in thread
From: Chris Wilson @ 2020-02-24 23:48 UTC (permalink / raw)
To: intel-gfx
Quoting Chris Wilson (2020-02-24 23:31:10)
> The engine->kernel_context is a special case for request emission. Since
> it is used as the barrier within the engine's wakeref, we must acquire the
> wakeref before submitting a request to the kernel_context.
>
> Reported-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
I finally hit the exact symptoms Lionel reported, so no this patch
doesn't fix that, but it is still a potential issue.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Manually acquire engine-wakeref around use of kernel_context
2020-02-24 23:31 [Intel-gfx] [PATCH] drm/i915: Manually acquire engine-wakeref around use of kernel_context Chris Wilson
2020-02-24 23:48 ` Chris Wilson
@ 2020-02-25 0:50 ` Patchwork
1 sibling, 0 replies; 3+ messages in thread
From: Patchwork @ 2020-02-25 0:50 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Manually acquire engine-wakeref around use of kernel_context
URL : https://patchwork.freedesktop.org/series/73878/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8000 -> Patchwork_16696
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_16696 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_16696, 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/Patchwork_16696/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_16696:
### IGT changes ###
#### Possible regressions ####
* igt@i915_module_load@reload:
- fi-hsw-peppy: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-hsw-peppy/igt@i915_module_load@reload.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-hsw-peppy/igt@i915_module_load@reload.html
Known issues
------------
Here are the changes found in Patchwork_16696 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_gt_lrc:
- fi-bwr-2160: [PASS][3] -> [INCOMPLETE][4] ([i915#695])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-bwr-2160/igt@i915_selftest@live_gt_lrc.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-bwr-2160/igt@i915_selftest@live_gt_lrc.html
* igt@kms_addfb_basic@addfb25-y-tiled:
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([CI#94] / [i915#402])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-tgl-y/igt@kms_addfb_basic@addfb25-y-tiled.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-tgl-y/igt@kms_addfb_basic@addfb25-y-tiled.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-tgl-y: [FAIL][7] ([CI#94]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-tgl-y/igt@gem_exec_suspend@basic-s4-devices.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-tgl-y/igt@gem_exec_suspend@basic-s4-devices.html
* igt@gem_render_linear_blits@basic:
- fi-tgl-y: [DMESG-WARN][9] ([CI#94] / [i915#402]) -> [PASS][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-tgl-y/igt@gem_render_linear_blits@basic.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-tgl-y/igt@gem_render_linear_blits@basic.html
* igt@i915_selftest@live_execlists:
- fi-bsw-kefka: [DMESG-FAIL][11] -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-bsw-kefka/igt@i915_selftest@live_execlists.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-bsw-kefka/igt@i915_selftest@live_execlists.html
* igt@i915_selftest@live_gem_contexts:
- fi-cml-s: [DMESG-FAIL][13] ([i915#877]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-cml-s/igt@i915_selftest@live_gem_contexts.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-cml-s/igt@i915_selftest@live_gem_contexts.html
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: [DMESG-WARN][15] ([i915#44]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
#### Warnings ####
* igt@i915_selftest@live_gt_lrc:
- fi-tgl-y: [DMESG-FAIL][17] ([CI#94] / [i915#1233]) -> [INCOMPLETE][18] ([CI#94] / [i915#1233])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-tgl-y/igt@i915_selftest@live_gt_lrc.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-tgl-y/igt@i915_selftest@live_gt_lrc.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][19] ([fdo#111407]) -> [FAIL][20] ([fdo#111096] / [i915#323])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8000/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[CI#94]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/94
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
[i915#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
[i915#323]: https://gitlab.freedesktop.org/drm/intel/issues/323
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#44]: https://gitlab.freedesktop.org/drm/intel/issues/44
[i915#695]: https://gitlab.freedesktop.org/drm/intel/issues/695
[i915#877]: https://gitlab.freedesktop.org/drm/intel/issues/877
Participating hosts (48 -> 45)
------------------------------
Additional (2): fi-byt-n2820 fi-cfl-8109u
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8000 -> Patchwork_16696
CI-20190529: 20190529
CI_DRM_8000: e231691d89abd1b3fff01e75f142e435b44b522f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5463: d519c80219ebe558cd2fa378f26f9d73f9e35310 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16696: 38ff2e8edc02e7792d6950ed5bef40d8e2f798a5 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
38ff2e8edc02 drm/i915: Manually acquire engine-wakeref around use of kernel_context
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16696/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-02-25 0:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-24 23:31 [Intel-gfx] [PATCH] drm/i915: Manually acquire engine-wakeref around use of kernel_context Chris Wilson
2020-02-24 23:48 ` Chris Wilson
2020-02-25 0:50 ` [Intel-gfx] ✗ Fi.CI.BAT: 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.