* [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation @ 2023-03-13 10:30 Nirmoy Das 2023-03-13 10:35 ` Janusz Krzysztofik ` (4 more replies) 0 siblings, 5 replies; 11+ messages in thread From: Nirmoy Das @ 2023-03-13 10:30 UTC (permalink / raw) To: intel-gfx; +Cc: stable, Chris Wilson, Thomas Hellström, Nirmoy Das debug_active_activate() expected ref->count to be zero which is not true anymore as __i915_active_activate() calls debug_active_activate() after incrementing the count. v2: No need to check for "ref->count == 1" as __i915_active_activate() already make sure of that. Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Thomas Hellström <thomas.hellstrom@intel.com> Cc: Andi Shyti <andi.shyti@linux.intel.com> Cc: intel-gfx@lists.freedesktop.org Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> Cc: <stable@vger.kernel.org> # v5.10+ Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> --- drivers/gpu/drm/i915/i915_active.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c index a9fea115f2d2..8ef93889061a 100644 --- a/drivers/gpu/drm/i915/i915_active.c +++ b/drivers/gpu/drm/i915/i915_active.c @@ -92,8 +92,7 @@ static void debug_active_init(struct i915_active *ref) static void debug_active_activate(struct i915_active *ref) { lockdep_assert_held(&ref->tree_lock); - if (!atomic_read(&ref->count)) /* before the first inc */ - debug_object_activate(ref, &active_debug_desc); + debug_object_activate(ref, &active_debug_desc); } static void debug_active_deactivate(struct i915_active *ref) -- 2.39.0 ^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das @ 2023-03-13 10:35 ` Janusz Krzysztofik 2023-03-13 11:46 ` [Intel-gfx] [PATCH] " Nirmoy Das ` (3 subsequent siblings) 4 siblings, 0 replies; 11+ messages in thread From: Janusz Krzysztofik @ 2023-03-13 10:35 UTC (permalink / raw) To: intel-gfx, Nirmoy Das Cc: stable, Chris Wilson, Thomas Hellström, Nirmoy Das On Monday, 13 March 2023 11:30:45 CET Nirmoy Das wrote: > debug_active_activate() expected ref->count to be zero > which is not true anymore as __i915_active_activate() calls > debug_active_activate() after incrementing the count. > > v2: No need to check for "ref->count == 1" as __i915_active_activate() > already make sure of that. > > Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") > Cc: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Cc: Thomas Hellström <thomas.hellstrom@intel.com> > Cc: Andi Shyti <andi.shyti@linux.intel.com> > Cc: intel-gfx@lists.freedesktop.org > Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> > Cc: <stable@vger.kernel.org> # v5.10+ > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> Reviewed-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> > --- > drivers/gpu/drm/i915/i915_active.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c > index a9fea115f2d2..8ef93889061a 100644 > --- a/drivers/gpu/drm/i915/i915_active.c > +++ b/drivers/gpu/drm/i915/i915_active.c > @@ -92,8 +92,7 @@ static void debug_active_init(struct i915_active *ref) > static void debug_active_activate(struct i915_active *ref) > { > lockdep_assert_held(&ref->tree_lock); > - if (!atomic_read(&ref->count)) /* before the first inc */ > - debug_object_activate(ref, &active_debug_desc); > + debug_object_activate(ref, &active_debug_desc); > } > > static void debug_active_deactivate(struct i915_active *ref) > ^ permalink raw reply [flat|nested] 11+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das 2023-03-13 10:35 ` Janusz Krzysztofik @ 2023-03-13 11:46 ` Nirmoy Das 2023-03-13 13:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork ` (2 subsequent siblings) 4 siblings, 0 replies; 11+ messages in thread From: Nirmoy Das @ 2023-03-13 11:46 UTC (permalink / raw) To: intel-gfx; +Cc: stable, Chris Wilson, Thomas Hellström, Nirmoy Das debug_active_activate() expected ref->count to be zero which is not true anymore as __i915_active_activate() calls debug_active_activate() after incrementing the count. v2: No need to check for "ref->count == 1" as __i915_active_activate() already make sure of that. References: https://gitlab.freedesktop.org/drm/intel/-/issues/6733 Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Thomas Hellström <thomas.hellstrom@intel.com> Cc: Andi Shyti <andi.shyti@linux.intel.com> Cc: intel-gfx@lists.freedesktop.org Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> Cc: <stable@vger.kernel.org> # v5.10+ Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> Reviewed-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> --- drivers/gpu/drm/i915/i915_active.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c index a9fea115f2d2..8ef93889061a 100644 --- a/drivers/gpu/drm/i915/i915_active.c +++ b/drivers/gpu/drm/i915/i915_active.c @@ -92,8 +92,7 @@ static void debug_active_init(struct i915_active *ref) static void debug_active_activate(struct i915_active *ref) { lockdep_assert_held(&ref->tree_lock); - if (!atomic_read(&ref->count)) /* before the first inc */ - debug_object_activate(ref, &active_debug_desc); + debug_object_activate(ref, &active_debug_desc); } static void debug_active_deactivate(struct i915_active *ref) -- 2.39.0 ^ permalink raw reply related [flat|nested] 11+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix missing debug object activation (rev3) 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das 2023-03-13 10:35 ` Janusz Krzysztofik 2023-03-13 11:46 ` [Intel-gfx] [PATCH] " Nirmoy Das @ 2023-03-13 13:13 ` Patchwork 2023-03-13 17:53 ` [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Andrzej Hajda 2023-03-14 14:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork 4 siblings, 0 replies; 11+ messages in thread From: Patchwork @ 2023-03-13 13:13 UTC (permalink / raw) To: Nirmoy Das; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 4781 bytes --] == Series Details == Series: drm/i915/active: Fix missing debug object activation (rev3) URL : https://patchwork.freedesktop.org/series/114981/ State : success == Summary == CI Bug Log - changes from CI_DRM_12851 -> Patchwork_114981v3 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/index.html Participating hosts (38 -> 37) ------------------------------ Missing (1): bat-atsm-1 Known issues ------------ Here are the changes found in Patchwork_114981v3 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_selftest@live@execlists: - fi-bsw-n3050: [PASS][1] -> [ABORT][2] ([i915#7911]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/fi-bsw-n3050/igt@i915_selftest@live@execlists.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/fi-bsw-n3050/igt@i915_selftest@live@execlists.html * igt@i915_selftest@live@hangcheck: - bat-dg2-11: [PASS][3] -> [ABORT][4] ([i915#7913]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/bat-dg2-11/igt@i915_selftest@live@hangcheck.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/bat-dg2-11/igt@i915_selftest@live@hangcheck.html * igt@i915_selftest@live@requests: - bat-rpls-2: [PASS][5] -> [ABORT][6] ([i915#4983] / [i915#7694] / [i915#7913]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/bat-rpls-2/igt@i915_selftest@live@requests.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/bat-rpls-2/igt@i915_selftest@live@requests.html * igt@kms_chamelium_hpd@common-hpd-after-suspend: - fi-bsw-nick: NOTRUN -> [SKIP][7] ([fdo#109271]) +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/fi-bsw-nick/igt@kms_chamelium_hpd@common-hpd-after-suspend.html - bat-dg1-5: NOTRUN -> [SKIP][8] ([i915#7828]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/bat-dg1-5/igt@kms_chamelium_hpd@common-hpd-after-suspend.html #### Possible fixes #### * igt@i915_selftest@live@execlists: - fi-bsw-nick: [ABORT][9] ([i915#7911] / [i915#7913]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/fi-bsw-nick/igt@i915_selftest@live@execlists.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/fi-bsw-nick/igt@i915_selftest@live@execlists.html * igt@i915_selftest@live@hangcheck: - bat-dg1-5: [ABORT][11] ([i915#4983]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/bat-dg1-5/igt@i915_selftest@live@hangcheck.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/bat-dg1-5/igt@i915_selftest@live@hangcheck.html - fi-skl-guc: [DMESG-WARN][13] ([i915#8073]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/fi-skl-guc/igt@i915_selftest@live@hangcheck.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/fi-skl-guc/igt@i915_selftest@live@hangcheck.html #### Warnings #### * igt@i915_selftest@live@slpc: - bat-rpls-1: [DMESG-FAIL][15] ([i915#6367]) -> [DMESG-FAIL][16] ([i915#6367] / [i915#6997]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/bat-rpls-1/igt@i915_selftest@live@slpc.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/bat-rpls-1/igt@i915_selftest@live@slpc.html [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983 [i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367 [i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997 [i915#7694]: https://gitlab.freedesktop.org/drm/intel/issues/7694 [i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828 [i915#7911]: https://gitlab.freedesktop.org/drm/intel/issues/7911 [i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913 [i915#8073]: https://gitlab.freedesktop.org/drm/intel/issues/8073 Build changes ------------- * Linux: CI_DRM_12851 -> Patchwork_114981v3 CI-20190529: 20190529 CI_DRM_12851: 6dda6adf7d6294bd28549db109981501eba02381 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_7191: a6766ee8a971366299671b06af8febc8192c0f74 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_114981v3: 6dda6adf7d6294bd28549db109981501eba02381 @ git://anongit.freedesktop.org/gfx-ci/linux ### Linux commits 51af89fcbe1e drm/i915/active: Fix missing debug object activation == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/index.html [-- Attachment #2: Type: text/html, Size: 5916 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das ` (2 preceding siblings ...) 2023-03-13 13:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork @ 2023-03-13 17:53 ` Andrzej Hajda 2023-03-14 14:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork 4 siblings, 0 replies; 11+ messages in thread From: Andrzej Hajda @ 2023-03-13 17:53 UTC (permalink / raw) To: Nirmoy Das, intel-gfx; +Cc: Thomas Hellström, stable, Chris Wilson On 13.03.2023 11:30, Nirmoy Das wrote: > debug_active_activate() expected ref->count to be zero > which is not true anymore as __i915_active_activate() calls > debug_active_activate() after incrementing the count. > > v2: No need to check for "ref->count == 1" as __i915_active_activate() > already make sure of that. > > Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") > Cc: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Cc: Thomas Hellström <thomas.hellstrom@intel.com> > Cc: Andi Shyti <andi.shyti@linux.intel.com> > Cc: intel-gfx@lists.freedesktop.org > Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> > Cc: <stable@vger.kernel.org> # v5.10+ > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com> Regards Andrzej > --- > drivers/gpu/drm/i915/i915_active.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c > index a9fea115f2d2..8ef93889061a 100644 > --- a/drivers/gpu/drm/i915/i915_active.c > +++ b/drivers/gpu/drm/i915/i915_active.c > @@ -92,8 +92,7 @@ static void debug_active_init(struct i915_active *ref) > static void debug_active_activate(struct i915_active *ref) > { > lockdep_assert_held(&ref->tree_lock); > - if (!atomic_read(&ref->count)) /* before the first inc */ > - debug_object_activate(ref, &active_debug_desc); > + debug_object_activate(ref, &active_debug_desc); > } > > static void debug_active_deactivate(struct i915_active *ref) ^ permalink raw reply [flat|nested] 11+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/active: Fix missing debug object activation (rev3) 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das ` (3 preceding siblings ...) 2023-03-13 17:53 ` [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Andrzej Hajda @ 2023-03-14 14:43 ` Patchwork 4 siblings, 0 replies; 11+ messages in thread From: Patchwork @ 2023-03-14 14:43 UTC (permalink / raw) To: Nirmoy Das; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 20725 bytes --] == Series Details == Series: drm/i915/active: Fix missing debug object activation (rev3) URL : https://patchwork.freedesktop.org/series/114981/ State : success == Summary == CI Bug Log - changes from CI_DRM_12851_full -> Patchwork_114981v3_full ==================================================== Summary ------- **SUCCESS** No regressions found. Participating hosts (8 -> 8) ------------------------------ No changes in participating hosts Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_114981v3_full: ### IGT changes ### #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@kms_cursor_legacy@cursor-vs-flip-varying-size: - {shard-tglu}: [SKIP][1] ([i915#1845]) -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-9/igt@kms_cursor_legacy@cursor-vs-flip-varying-size.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-4/igt@kms_cursor_legacy@cursor-vs-flip-varying-size.html Known issues ------------ Here are the changes found in Patchwork_114981v3_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_fair@basic-none-solo@rcs0: - shard-apl: [PASS][3] -> [FAIL][4] ([i915#2842]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-apl4/igt@gem_exec_fair@basic-none-solo@rcs0.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-apl7/igt@gem_exec_fair@basic-none-solo@rcs0.html * igt@gen9_exec_parse@allowed-all: - shard-apl: [PASS][5] -> [ABORT][6] ([i915#5566]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-apl6/igt@gen9_exec_parse@allowed-all.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-apl7/igt@gen9_exec_parse@allowed-all.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-apl: [PASS][7] -> [FAIL][8] ([i915#2346]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-apl2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-apl2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html #### Possible fixes #### * igt@api_intel_bb@object-reloc-keep-cache: - {shard-rkl}: [SKIP][9] ([i915#3281]) -> [PASS][10] +4 similar issues [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-6/igt@api_intel_bb@object-reloc-keep-cache.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-5/igt@api_intel_bb@object-reloc-keep-cache.html * igt@debugfs_test@read_all_entries_display_on: - shard-apl: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-apl4/igt@debugfs_test@read_all_entries_display_on.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-apl1/igt@debugfs_test@read_all_entries_display_on.html * igt@drm_fdinfo@virtual-idle: - {shard-rkl}: [FAIL][13] ([i915#7742]) -> [PASS][14] +1 similar issue [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-6/igt@drm_fdinfo@virtual-idle.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-5/igt@drm_fdinfo@virtual-idle.html * igt@feature_discovery@psr1: - {shard-rkl}: [SKIP][15] ([i915#658]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-3/igt@feature_discovery@psr1.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-6/igt@feature_discovery@psr1.html * igt@gem_ctx_persistence@engines-hang@bcs0: - {shard-rkl}: [SKIP][17] ([i915#6252]) -> [PASS][18] +1 similar issue [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-5/igt@gem_ctx_persistence@engines-hang@bcs0.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-4/igt@gem_ctx_persistence@engines-hang@bcs0.html * igt@gem_eio@in-flight-suspend: - {shard-rkl}: [FAIL][19] ([fdo#103375]) -> [PASS][20] [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-4/igt@gem_eio@in-flight-suspend.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-2/igt@gem_eio@in-flight-suspend.html * igt@gem_exec_endless@dispatch@bcs0: - {shard-rkl}: [SKIP][21] ([i915#6247]) -> [PASS][22] [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-5/igt@gem_exec_endless@dispatch@bcs0.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-4/igt@gem_exec_endless@dispatch@bcs0.html * igt@gem_exec_fair@basic-pace-share@rcs0: - shard-glk: [FAIL][23] ([i915#2842]) -> [PASS][24] [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-glk3/igt@gem_exec_fair@basic-pace-share@rcs0.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-glk3/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@gem_set_tiling_vs_pwrite: - {shard-rkl}: [SKIP][25] ([i915#3282]) -> [PASS][26] +2 similar issues [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-6/igt@gem_set_tiling_vs_pwrite.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-5/igt@gem_set_tiling_vs_pwrite.html * igt@i915_hangman@gt-engine-error@bcs0: - {shard-rkl}: [SKIP][27] ([i915#6258]) -> [PASS][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-5/igt@i915_hangman@gt-engine-error@bcs0.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-4/igt@i915_hangman@gt-engine-error@bcs0.html * igt@i915_pm_dc@dc9-dpms: - {shard-rkl}: [SKIP][29] ([i915#4281]) -> [PASS][30] [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-4/igt@i915_pm_dc@dc9-dpms.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-2/igt@i915_pm_dc@dc9-dpms.html * igt@i915_pm_rpm@dpms-mode-unset-lpsp: - {shard-dg1}: [SKIP][31] ([i915#1397]) -> [PASS][32] [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-dg1-13/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-dg1-14/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic: - {shard-rkl}: [SKIP][33] ([i915#1845] / [i915#4098]) -> [PASS][34] +13 similar issues [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-3/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-6/igt@kms_cursor_legacy@flip-vs-cursor-atomic.html * igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions: - {shard-tglu}: [SKIP][35] ([i915#1845]) -> [PASS][36] +8 similar issues [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-9/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-7/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html * igt@kms_fbcon_fbt@fbc-suspend: - {shard-tglu}: [FAIL][37] ([i915#4767]) -> [PASS][38] [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-10/igt@kms_fbcon_fbt@fbc-suspend.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-2/igt@kms_fbcon_fbt@fbc-suspend.html * igt@kms_frontbuffer_tracking@fbc-1p-indfb-fliptrack-mmap-gtt: - {shard-tglu}: [SKIP][39] ([i915#1849]) -> [PASS][40] +9 similar issues [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-9/igt@kms_frontbuffer_tracking@fbc-1p-indfb-fliptrack-mmap-gtt.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-4/igt@kms_frontbuffer_tracking@fbc-1p-indfb-fliptrack-mmap-gtt.html * igt@kms_frontbuffer_tracking@psr-rgb565-draw-render: - {shard-rkl}: [SKIP][41] ([i915#1849] / [i915#4098]) -> [PASS][42] +5 similar issues [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-3/igt@kms_frontbuffer_tracking@psr-rgb565-draw-render.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-6/igt@kms_frontbuffer_tracking@psr-rgb565-draw-render.html * igt@kms_plane@plane-panning-top-left@pipe-a-planes: - {shard-rkl}: [SKIP][43] ([i915#1849]) -> [PASS][44] +1 similar issue [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-3/igt@kms_plane@plane-panning-top-left@pipe-a-planes.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-6/igt@kms_plane@plane-panning-top-left@pipe-a-planes.html - {shard-tglu}: [SKIP][45] ([i915#1849] / [i915#3558]) -> [PASS][46] +1 similar issue [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-6/igt@kms_plane@plane-panning-top-left@pipe-a-planes.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-3/igt@kms_plane@plane-panning-top-left@pipe-a-planes.html * igt@kms_psr@cursor_mmap_gtt: - {shard-rkl}: [SKIP][47] ([i915#1072]) -> [PASS][48] [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-rkl-3/igt@kms_psr@cursor_mmap_gtt.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-rkl-6/igt@kms_psr@cursor_mmap_gtt.html * igt@kms_universal_plane@universal-plane-pipe-b-sanity: - {shard-tglu}: [SKIP][49] ([fdo#109274]) -> [PASS][50] [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-6/igt@kms_universal_plane@universal-plane-pipe-b-sanity.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-3/igt@kms_universal_plane@universal-plane-pipe-b-sanity.html * igt@kms_vblank@pipe-d-query-forked: - {shard-tglu}: [SKIP][51] ([i915#1845] / [i915#7651]) -> [PASS][52] +30 similar issues [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-9/igt@kms_vblank@pipe-d-query-forked.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-4/igt@kms_vblank@pipe-d-query-forked.html * igt@perf@polling-small-buf: - {shard-tglu}: [FAIL][53] ([i915#1722]) -> [PASS][54] [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12851/shard-tglu-9/igt@perf@polling-small-buf.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/shard-tglu-7/igt@perf@polling-small-buf.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375 [fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274 [fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280 [fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289 [fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295 [fdo#109302]: https://bugs.freedesktop.org/show_bug.cgi?id=109302 [fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308 [fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309 [fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313 [fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315 [fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189 [fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542 [fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723 [fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068 [fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614 [fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615 [fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825 [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827 [fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283 [i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072 [i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132 [i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397 [i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722 [i915#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755 [i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825 [i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839 [i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845 [i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849 [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982 [i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346 [i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437 [i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527 [i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575 [i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582 [i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587 [i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658 [i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672 [i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681 [i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280 [i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842 [i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856 [i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920 [i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116 [i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281 [i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282 [i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291 [i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297 [i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299 [i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323 [i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359 [i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458 [i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546 [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555 [i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558 [i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591 [i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637 [i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638 [i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689 [i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708 [i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734 [i915#3825]: https://gitlab.freedesktop.org/drm/intel/issues/3825 [i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840 [i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886 [i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955 [i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989 [i915#404]: https://gitlab.freedesktop.org/drm/intel/issues/404 [i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070 [i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077 [i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083 [i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098 [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212 [i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213 [i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215 [i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426 [i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270 [i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281 [i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433 [i915#4349]: https://gitlab.freedesktop.org/drm/intel/issues/4349 [i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538 [i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454 [i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613 [i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767 [i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812 [i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833 [i915#4854]: https://gitlab.freedesktop.org/drm/intel/issues/4854 [i915#4859]: https://gitlab.freedesktop.org/drm/intel/issues/4859 [i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860 [i915#4880]: https://gitlab.freedesktop.org/drm/intel/issues/4880 [i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176 [i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235 [i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286 [i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289 [i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325 [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533 [i915#5431]: https://gitlab.freedesktop.org/drm/intel/issues/5431 [i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439 [i915#5461]: https://gitlab.freedesktop.org/drm/intel/issues/5461 [i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563 [i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566 [i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723 [i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095 [i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227 [i915#6247]: https://gitlab.freedesktop.org/drm/intel/issues/6247 [i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248 [i915#6252]: https://gitlab.freedesktop.org/drm/intel/issues/6252 [i915#6258]: https://gitlab.freedesktop.org/drm/intel/issues/6258 [i915#6301]: https://gitlab.freedesktop.org/drm/intel/issues/6301 [i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433 [i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497 [i915#6524]: https://gitlab.freedesktop.org/drm/intel/issues/6524 [i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658 [i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621 [i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768 [i915#6944]: https://gitlab.freedesktop.org/drm/intel/issues/6944 [i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953 [i915#7037]: https://gitlab.freedesktop.org/drm/intel/issues/7037 [i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116 [i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118 [i915#7128]: https://gitlab.freedesktop.org/drm/intel/issues/7128 [i915#7178]: https://gitlab.freedesktop.org/drm/intel/issues/7178 [i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561 [i915#7651]: https://gitlab.freedesktop.org/drm/intel/issues/7651 [i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697 [i915#7701]: https://gitlab.freedesktop.org/drm/intel/issues/7701 [i915#7711]: https://gitlab.freedesktop.org/drm/intel/issues/7711 [i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742 [i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828 [i915#7949]: https://gitlab.freedesktop.org/drm/intel/issues/7949 [i915#7957]: https://gitlab.freedesktop.org/drm/intel/issues/7957 [i915#8150]: https://gitlab.freedesktop.org/drm/intel/issues/8150 [i915#8151]: https://gitlab.freedesktop.org/drm/intel/issues/8151 [i915#8152]: https://gitlab.freedesktop.org/drm/intel/issues/8152 [i915#8282]: https://gitlab.freedesktop.org/drm/intel/issues/8282 Build changes ------------- * Linux: CI_DRM_12851 -> Patchwork_114981v3 CI-20190529: 20190529 CI_DRM_12851: 6dda6adf7d6294bd28549db109981501eba02381 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_7191: a6766ee8a971366299671b06af8febc8192c0f74 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_114981v3: 6dda6adf7d6294bd28549db109981501eba02381 @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_114981v3/index.html [-- Attachment #2: Type: text/html, Size: 14988 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation @ 2023-03-10 14:11 Nirmoy Das 2023-03-10 15:19 ` Janusz Krzysztofik 0 siblings, 1 reply; 11+ messages in thread From: Nirmoy Das @ 2023-03-10 14:11 UTC (permalink / raw) To: intel-gfx; +Cc: stable, Chris Wilson, Thomas Hellström, Nirmoy Das debug_active_activate() expected ref->count to be zero which is not true anymore as __i915_active_activate() calls debug_active_activate() after incrementing the count. Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Thomas Hellström <thomas.hellstrom@intel.com> Cc: Andi Shyti <andi.shyti@linux.intel.com> Cc: intel-gfx@lists.freedesktop.org Cc: <stable@vger.kernel.org> # v5.10+ Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> --- drivers/gpu/drm/i915/i915_active.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c index a9fea115f2d2..1c3066eb359a 100644 --- a/drivers/gpu/drm/i915/i915_active.c +++ b/drivers/gpu/drm/i915/i915_active.c @@ -92,7 +92,7 @@ static void debug_active_init(struct i915_active *ref) static void debug_active_activate(struct i915_active *ref) { lockdep_assert_held(&ref->tree_lock); - if (!atomic_read(&ref->count)) /* before the first inc */ + if (atomic_read(&ref->count) == 1) /* after the first inc */ debug_object_activate(ref, &active_debug_desc); } -- 2.39.0 ^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation 2023-03-10 14:11 [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation Nirmoy Das @ 2023-03-10 15:19 ` Janusz Krzysztofik 2023-03-10 16:48 ` Das, Nirmoy 0 siblings, 1 reply; 11+ messages in thread From: Janusz Krzysztofik @ 2023-03-10 15:19 UTC (permalink / raw) To: intel-gfx; +Cc: Nirmoy Das, Thomas Hellström, stable, Chris Wilson Hi Nirmoy, On Friday, 10 March 2023 15:11:38 CET Nirmoy Das wrote: > debug_active_activate() expected ref->count to be zero > which is not true anymore as __i915_active_activate() calls > debug_active_activate() after incrementing the count. > > Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active callback") > Cc: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Cc: Thomas Hellström <thomas.hellstrom@intel.com> > Cc: Andi Shyti <andi.shyti@linux.intel.com> > Cc: intel-gfx@lists.freedesktop.org > Cc: <stable@vger.kernel.org> # v5.10+ > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> > --- > drivers/gpu/drm/i915/i915_active.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/ i915_active.c > index a9fea115f2d2..1c3066eb359a 100644 > --- a/drivers/gpu/drm/i915/i915_active.c > +++ b/drivers/gpu/drm/i915/i915_active.c > @@ -92,7 +92,7 @@ static void debug_active_init(struct i915_active *ref) > static void debug_active_activate(struct i915_active *ref) > { > lockdep_assert_held(&ref->tree_lock); > - if (!atomic_read(&ref->count)) /* before the first inc */ > + if (atomic_read(&ref->count) == 1) /* after the first inc */ While that's obviously better than never calling debug_active_activate(), I'm wondering how likely we can still miss it because the counter being incremented, e.g. via i915_active_acquire_if_busy(), by a concurrent thread. Since __i915_active_activate() is the only user and its decision making step is serialized against itself with a spinlock, couldn't we better call debug_object_activate() unconditionally here? Thanks, Janusz > debug_object_activate(ref, &active_debug_desc); > } > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation 2023-03-10 15:19 ` Janusz Krzysztofik @ 2023-03-10 16:48 ` Das, Nirmoy 2023-03-13 9:55 ` Janusz Krzysztofik 0 siblings, 1 reply; 11+ messages in thread From: Das, Nirmoy @ 2023-03-10 16:48 UTC (permalink / raw) To: Janusz Krzysztofik, intel-gfx Cc: Thomas Hellström, Chris Wilson, stable, Nirmoy Das Hi Janusz, On 3/10/2023 4:19 PM, Janusz Krzysztofik wrote: > Hi Nirmoy, > > On Friday, 10 March 2023 15:11:38 CET Nirmoy Das wrote: >> debug_active_activate() expected ref->count to be zero >> which is not true anymore as __i915_active_activate() calls >> debug_active_activate() after incrementing the count. >> >> Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref->active > callback") >> Cc: Chris Wilson <chris@chris-wilson.co.uk> >> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> Cc: Thomas Hellström <thomas.hellstrom@intel.com> >> Cc: Andi Shyti <andi.shyti@linux.intel.com> >> Cc: intel-gfx@lists.freedesktop.org >> Cc: <stable@vger.kernel.org> # v5.10+ >> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> >> --- >> drivers/gpu/drm/i915/i915_active.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/ > i915_active.c >> index a9fea115f2d2..1c3066eb359a 100644 >> --- a/drivers/gpu/drm/i915/i915_active.c >> +++ b/drivers/gpu/drm/i915/i915_active.c >> @@ -92,7 +92,7 @@ static void debug_active_init(struct i915_active *ref) >> static void debug_active_activate(struct i915_active *ref) >> { >> lockdep_assert_held(&ref->tree_lock); >> - if (!atomic_read(&ref->count)) /* before the first inc */ >> + if (atomic_read(&ref->count) == 1) /* after the first inc */ > While that's obviously better than never calling debug_active_activate(), I'm > wondering how likely we can still miss it because the counter being > incremented, e.g. via i915_active_acquire_if_busy(), by a concurrent thread. > Since __i915_active_activate() is the only user and its decision making step > is serialized against itself with a spinlock, couldn't we better call > debug_object_activate() unconditionally here? Yes, we can call debug_object_activate() without checking ref->count. Also we can remove the ref-count check for debug_active_deactivate() as this is wrapped with "atomic_dec_and_lock_irqsave(&ref->count, &ref->tree_lock, flags)". I think it makes sense to keep this patch as it is so it can be backported easily. I can add another patch to remove unnecessary ref->count checks. Regards, Nirmoy > > Thanks, > Janusz > >> debug_object_activate(ref, &active_debug_desc); >> } >> >> > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation 2023-03-10 16:48 ` Das, Nirmoy @ 2023-03-13 9:55 ` Janusz Krzysztofik 2023-03-13 10:33 ` Das, Nirmoy 0 siblings, 1 reply; 11+ messages in thread From: Janusz Krzysztofik @ 2023-03-13 9:55 UTC (permalink / raw) To: intel-gfx, Das, Nirmoy Cc: Thomas Hellström, Chris Wilson, stable, Nirmoy Das On Friday, 10 March 2023 17:48:10 CET Das, Nirmoy wrote: > Hi Janusz, > > On 3/10/2023 4:19 PM, Janusz Krzysztofik wrote: > > Hi Nirmoy, > > > > On Friday, 10 March 2023 15:11:38 CET Nirmoy Das wrote: > >> debug_active_activate() expected ref->count to be zero > >> which is not true anymore as __i915_active_activate() calls > >> debug_active_activate() after incrementing the count. > >> > >> Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref- >active > > callback") > >> Cc: Chris Wilson <chris@chris-wilson.co.uk> > >> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > >> Cc: Thomas Hellström <thomas.hellstrom@intel.com> > >> Cc: Andi Shyti <andi.shyti@linux.intel.com> > >> Cc: intel-gfx@lists.freedesktop.org > >> Cc: <stable@vger.kernel.org> # v5.10+ > >> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> > >> --- > >> drivers/gpu/drm/i915/i915_active.c | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/ > > i915_active.c > >> index a9fea115f2d2..1c3066eb359a 100644 > >> --- a/drivers/gpu/drm/i915/i915_active.c > >> +++ b/drivers/gpu/drm/i915/i915_active.c > >> @@ -92,7 +92,7 @@ static void debug_active_init(struct i915_active *ref) > >> static void debug_active_activate(struct i915_active *ref) > >> { > >> lockdep_assert_held(&ref->tree_lock); > >> - if (!atomic_read(&ref->count)) /* before the first inc */ > >> + if (atomic_read(&ref->count) == 1) /* after the first inc */ > > While that's obviously better than never calling debug_active_activate(), I'm > > wondering how likely we can still miss it because the counter being > > incremented, e.g. via i915_active_acquire_if_busy(), by a concurrent thread. > > Since __i915_active_activate() is the only user and its decision making step > > is serialized against itself with a spinlock, couldn't we better call > > debug_object_activate() unconditionally here? > > > Yes, we can call debug_object_activate() without checking ref->count. > Also we can remove the ref-count check for > > debug_active_deactivate() as this is wrapped with > "atomic_dec_and_lock_irqsave(&ref->count, &ref->tree_lock, flags)". > > > I think it makes sense to keep this patch as it is so it can be > backported easily. I can add another patch to remove > > unnecessary ref->count checks. Looking at 5.10, I can't understand how dropping the check instead of replacing it with a still problematic one could make backporting less easy. Thanks, Janusz > > > Regards, > > Nirmoy > > > > > > Thanks, > > Janusz > > > >> debug_object_activate(ref, &active_debug_desc); > >> } > >> > >> > > > > > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation 2023-03-13 9:55 ` Janusz Krzysztofik @ 2023-03-13 10:33 ` Das, Nirmoy 0 siblings, 0 replies; 11+ messages in thread From: Das, Nirmoy @ 2023-03-13 10:33 UTC (permalink / raw) To: Janusz Krzysztofik, intel-gfx Cc: Thomas Hellström, Chris Wilson, stable, Nirmoy Das On 3/13/2023 10:55 AM, Janusz Krzysztofik wrote: > On Friday, 10 March 2023 17:48:10 CET Das, Nirmoy wrote: >> Hi Janusz, >> >> On 3/10/2023 4:19 PM, Janusz Krzysztofik wrote: >>> Hi Nirmoy, >>> >>> On Friday, 10 March 2023 15:11:38 CET Nirmoy Das wrote: >>>> debug_active_activate() expected ref->count to be zero >>>> which is not true anymore as __i915_active_activate() calls >>>> debug_active_activate() after incrementing the count. >>>> >>>> Fixes: 04240e30ed06 ("drm/i915: Skip taking acquire mutex for no ref- >> active >>> callback") >>>> Cc: Chris Wilson <chris@chris-wilson.co.uk> >>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >>>> Cc: Thomas Hellström <thomas.hellstrom@intel.com> >>>> Cc: Andi Shyti <andi.shyti@linux.intel.com> >>>> Cc: intel-gfx@lists.freedesktop.org >>>> Cc: <stable@vger.kernel.org> # v5.10+ >>>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com> >>>> --- >>>> drivers/gpu/drm/i915/i915_active.c | 2 +- >>>> 1 file changed, 1 insertion(+), 1 deletion(-) >>>> >>>> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/ >>> i915_active.c >>>> index a9fea115f2d2..1c3066eb359a 100644 >>>> --- a/drivers/gpu/drm/i915/i915_active.c >>>> +++ b/drivers/gpu/drm/i915/i915_active.c >>>> @@ -92,7 +92,7 @@ static void debug_active_init(struct i915_active *ref) >>>> static void debug_active_activate(struct i915_active *ref) >>>> { >>>> lockdep_assert_held(&ref->tree_lock); >>>> - if (!atomic_read(&ref->count)) /* before the first inc */ >>>> + if (atomic_read(&ref->count) == 1) /* after the first inc */ >>> While that's obviously better than never calling debug_active_activate(), > I'm >>> wondering how likely we can still miss it because the counter being >>> incremented, e.g. via i915_active_acquire_if_busy(), by a concurrent > thread. >>> Since __i915_active_activate() is the only user and its decision making > step >>> is serialized against itself with a spinlock, couldn't we better call >>> debug_object_activate() unconditionally here? >> >> Yes, we can call debug_object_activate() without checking ref->count. >> Also we can remove the ref-count check for >> >> debug_active_deactivate() as this is wrapped with >> "atomic_dec_and_lock_irqsave(&ref->count, &ref->tree_lock, flags)". >> >> >> I think it makes sense to keep this patch as it is so it can be >> backported easily. I can add another patch to remove >> >> unnecessary ref->count checks. > Looking at 5.10, I can't understand how dropping the check instead of > replacing it with a still problematic one could make backporting less easy. Indeed, I thought 5.10 is pretty far in the past but I was wrong. I can apply the modified patch. Sent out a v2 Thanks, Nirmoy > > Thanks, > Janusz > > >> >> Regards, >> >> Nirmoy >> >> >>> Thanks, >>> Janusz >>> >>>> debug_object_activate(ref, &active_debug_desc); >>>> } >>>> >>>> >>> >>> > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2023-03-14 14:43 UTC | newest] Thread overview: 11+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2023-03-13 10:30 [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Nirmoy Das 2023-03-13 10:35 ` Janusz Krzysztofik 2023-03-13 11:46 ` [Intel-gfx] [PATCH] " Nirmoy Das 2023-03-13 13:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork 2023-03-13 17:53 ` [Intel-gfx] [PATCH v2] drm/i915/active: Fix missing debug object activation Andrzej Hajda 2023-03-14 14:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/active: Fix missing debug object activation (rev3) Patchwork -- strict thread matches above, loose matches on Subject: below -- 2023-03-10 14:11 [Intel-gfx] [PATCH] drm/i915/active: Fix missing debug object activation Nirmoy Das 2023-03-10 15:19 ` Janusz Krzysztofik 2023-03-10 16:48 ` Das, Nirmoy 2023-03-13 9:55 ` Janusz Krzysztofik 2023-03-13 10:33 ` Das, Nirmoy
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).